Earlier quoted context omitted.
It was already quite easy to get GPT-4 to output json. You just append ‘reply in json with this format’ and it does a really good job. GPT-3.5 was very haphazard though and needs extensive babysitting and reminding, so if this makes gpt3 better then it’s useful - it does have an annoying disclaimer though that ‘it may not reply with valid json’ so we’ll still have to do some sense checks into he output. I have been u…
> You just append ‘reply in json with this format’ and it does a really good job. It does an ok job. Except when it doesn't. Definitely misses a lot of the time, sometimes on prompts that succeeded on previous runs.
Native JSON Output from GPT-4
131–140 of 258 posts
Re: Native JSON Output from GPT-4
#132i think people are underestimating the potential here for agents building - it is now a lot easier for GPT4 to call other models, or itself. while i was taking notes for our emergency pod yesterday ( https://www.latent.space/p/function-agents ) we had this interesting debate with Simon Willison on just how many functions will be supplied to this API. Simon thinks it will be "deep" rather than "wide" - eg a few functi…
It was already quite easy to get GPT-4 to output json. You just append ‘reply in json with this format’ and it does a really good job. GPT-3.5 was very haphazard though and needs extensive babysitting and reminding, so if this makes gpt3 better then it’s useful - it does have an annoying disclaimer though that ‘it may not reply with valid json’ so we’ll still have to do some sense checks into he output. I have been u…
This lets me specify general requirements (not just JSON structure) inline with the schema and in a very detailed and structured manor.
Re: Native JSON Output from GPT-4
#133Earlier quoted context omitted.
Wow your brand is huge. Crazy growth. i wonder how much these subtle mentions on forums help
They're the only one commenter on HN I noticed keeps writing "smol" instead of "small", and is associated with projects with "smol" in their name. Surely I'm not the only one who missed it being a meme around 2015 or sth., and finds this word/use jarring - and therefore very attention-grabbing? Wonder how much that helps with marketing. This is meant with no negative intentions. It's just that 'swyx was, in my mind,…
Re: Native JSON Output from GPT-4
#134i think people are underestimating the potential here for agents building - it is now a lot easier for GPT4 to call other models, or itself. while i was taking notes for our emergency pod yesterday ( https://www.latent.space/p/function-agents ) we had this interesting debate with Simon Willison on just how many functions will be supplied to this API. Simon thinks it will be "deep" rather than "wide" - eg a few functi…
GPT-4 was already a massive improvement on 3.5 in terms of replying consistently in a certain JSON structure - I often don't even need to give examples, just a sentence describing the format. It's great to see they're making it even better, but where I'm currently hitting the limit still in GPT-4 for "shelling out" is about it being truly "creative" or "introspective" about "do I need to ask for clarifications" or "c…
Re: Native JSON Output from GPT-4
#135Earlier quoted context omitted.
Did you try using the API and providing a very clear system message followed by several examples that were pure JSON?
Yep. I even gave it a JSON schema file to use. It just wouldn't stop added extra verbage.
Re: Native JSON Output from GPT-4
#136Earlier quoted context omitted.
Not that it matters now but just doing something like this works 99% of the time or more with 4 and 90% with 3.5. It is VERY IMPORTANT that you respond in valid JSON ONLY. Nothing before or after. Make sure to escape all strings. Use this format: {“some_variable”: [describe the variable purpose]}
Wouldn't you use traditional software to validate the JSON, then ask chatgpt to try again if it wasn't right?
Re: Native JSON Output from GPT-4
#137i think people are underestimating the potential here for agents building - it is now a lot easier for GPT4 to call other models, or itself. while i was taking notes for our emergency pod yesterday ( https://www.latent.space/p/function-agents ) we had this interesting debate with Simon Willison on just how many functions will be supplied to this API. Simon thinks it will be "deep" rather than "wide" - eg a few functi…
It was already quite easy to get GPT-4 to output json. You just append ‘reply in json with this format’ and it does a really good job. GPT-3.5 was very haphazard though and needs extensive babysitting and reminding, so if this makes gpt3 better then it’s useful - it does have an annoying disclaimer though that ‘it may not reply with valid json’ so we’ll still have to do some sense checks into he output. I have been u…
Re: Native JSON Output from GPT-4
#138Earlier quoted context omitted.
It was already quite easy to get GPT-4 to output json. You just append ‘reply in json with this format’ and it does a really good job. GPT-3.5 was very haphazard though and needs extensive babysitting and reminding, so if this makes gpt3 better then it’s useful - it does have an annoying disclaimer though that ‘it may not reply with valid json’ so we’ll still have to do some sense checks into he output. I have been u…
In a production system, you don’t need easy to do most of the time, you need easy without fail.
I think a better way to reply to the author would have been "how often does it fail"?
Every system will have outages, it's just a matter of how much money you can throw at the problem to reduce them.
Re: Native JSON Output from GPT-4
#139Earlier quoted context omitted.
In a production system, you don’t need easy to do most of the time, you need easy without fail.
Ok, just playing devil's advocate here. How many FAANG companies have you seen have an outage this year? What's their budget? I think a better way to reply to the author would have been "how often does it fail"? Every system will have outages, it's just a matter of how much money you can throw at the problem to reduce them.