> It's clear that if you wanted a "carrot dagger" in your json, you'd need to define it beforehand:
No, only if you want to explicitly limit it to a set of options. You can have freeform fields, just like the jsonschema I provided. If you look at the example there's a character name which has a constrained length but is not limited to a set of options:
class Character(BaseModel):
name: constr(max_length=10)
age: int
armor: Armor
weapon: Weapon
strength: int
The name there can be anything you want. This tool is, unfortunately, outrageously slow so I put the json schema above with a few fixes into jsonformer and downloaded a small model and used it to convert the GPT4 description into valid json:
{
"backstory":"Born in the tranquil meadows of Veggie",
"weapons":[
{
"name":"Leek Lance",
"description":"A long, green and white lance made from a leek",
"weapon_type":"distance",
"range":100.0,
"damage":75.0
},
{
"name":"Carrot Dagger",
"description":"A short, pointed dagger. It's sharp",
"weapon_type":"close",
"range":10.0,
"damage":50.0
}
],
"name":"Sir Turnip Thistlebrook"
}
> Not arbitrary.
Well exactly. If you want to support arbitrary requests while constraining the output, tools like this are an easy approach and I'm not sure what else comes close. An interactive character design flow would have something like the above as the defined output and you could just keep asking for alterations as a human would ("make it more whimsical" or "not a king, something lower class") and have useful structured output
> See my casting-to-type analogy. The point I'm trying really hard to get across is that generating free-form text is all nice and cool, but if you want to give it structure, you need to have the entire structure defined before-hand, otherwise the text that can't be made to conform to it simply won't.
The structure, sure. But the content can be extremely varied.
Thanks for the demonstration. Well, maybe I did understimate the tool after all, although I'd prefer to see the entire session (prompt, grammar, and all the interactions) to be fully convinced.
I suspect though that the reason the tool was "outrageously slow" in your experiment is that you gave a very general grammar. Constraining it more (by giving exact descriptions of weapons) would perhaps make it work faster.
Also, it's obvious that while you'll get valid json like that, you have no guarantee that the contents will always match your request. This time you got a carrot dagger (again- I'd like to see the prompt that led to that, please), next time you might not.
Happy to help, my current focus is on llms and how to understand them (pros, cons, how to use them safely and where they can fit into your workflow) so opportunities to talk through these things are useful for me.
> I suspect though that the reason the tool was "outrageously slow" in your experiment is that you gave a very general grammar
Actually even smallish ones caused problems but jsonformer (a similar tool) worked fine. Not sure what the issue is with this one, I couldn't get it to complete. Not sure if I've got the hacked together code I used to get the json, I was using very small models which didn't help but my internet is slow and I couldn't load anything decent in the time so some of the testing was "here's an llms jsonish output, fix it to this exact schema". Smaller models needed more hand holding. Gpt2 had no idea how to deal with it.
For jsonformer the grammar was near identical to what I posted before, I fixed a couple of typos I think.
Personally the flow of:
Reason about the problem
Write in english
Convert to JSON
- use a tool like this to fix broken JSON
Is a workflow I think is very applicable (you can use different models for any step too).
> again- I'd like to see the prompt that led to that, please
Sure, that was from gpt4, which actually was either fine or decent if given the jsonschema.
Here's the original prompt and the full response that had a full backstory:
> fun but not over the top character from the middle ages, with relevant weapons and a backstory. Game theme is a world populated by anthropomorphic vegetables
It's a shame you can't use some of these tools with gpt4, it's in a class of its own.
> Also, it's obvious that while you'll get valid json like that, you have no guarantee that the contents will always match your request
Yeah absolutely. You need to be doing something simple enough for the llm in use to reliably generate sensible output, tools like this then let you integrate that into other systems. How best to use llms really comes into how to pick a good one for the use case and how critical errors are - proposing d&d characters is a very low risk option (human oversight, no automatic application, errors are mostly just annoying, fixing is easy).
No, only if you want to explicitly limit it to a set of options. You can have freeform fields, just like the jsonschema I provided. If you look at the example there's a character name which has a constrained length but is not limited to a set of options:
The name there can be anything you want. This tool is, unfortunately, outrageously slow so I put the json schema above with a few fixes into jsonformer and downloaded a small model and used it to convert the GPT4 description into valid json: > Not arbitrary.Well exactly. If you want to support arbitrary requests while constraining the output, tools like this are an easy approach and I'm not sure what else comes close. An interactive character design flow would have something like the above as the defined output and you could just keep asking for alterations as a human would ("make it more whimsical" or "not a king, something lower class") and have useful structured output
> See my casting-to-type analogy. The point I'm trying really hard to get across is that generating free-form text is all nice and cool, but if you want to give it structure, you need to have the entire structure defined before-hand, otherwise the text that can't be made to conform to it simply won't.
The structure, sure. But the content can be extremely varied.