Earlier quoted context omitted.
even with gpt 4, it hallucinates enough that it’s not reliable, forgetting to open/close brackets and quotes. This sounds like it’d be a big improvement.
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]}
Native JSON Output from GPT-4
121–130 of 258 posts
Re: Native JSON Output from GPT-4
#122Earlier quoted context omitted.
Not GP, but it's still the latter...i've been (im)patiently waiting. From their blog post the other day: With these updates, we’ll be inviting many more people from the waitlist to try GPT-4 over the coming weeks, with the intent to remove the waitlist entirely with this model. Thank you to everyone who has been patiently waiting, we are excited to see what you build with GPT-4!
If you put contact info in your HN profile - especially an email address that matches one you use to login to openai, someone will probably give you access... Anyone with access can share it with any other user via the 'invite to organisation' feature. Obviously that allows the invited person do requests billed to the inviter, but since most experiments are only a few cents that doesn't really matter much in practice…
Re: Native JSON Output from GPT-4
#123After reading the docs for the new ChatGPT function calling yesterday, it's structured and/or typed data for GPT input or output that's the key feature of these new models. The ReAct flow of tool selection that it provides is secondary. As this post notes, you don't even need to the full flow of passing a function result back to the model: getting structured data from ChatGPT in itself has a lot of fun and practical…
What's the implication of this new change for Microsoft Guidance, LMQL, Langchain, etc.? It looks like much of their functionality (controlling model output) just became obsolete. Am I missing something?
* https://github.com/hwchase17/langchain/pull/6099/files
* https://github.com/hwchase17/langchain/issues/6104
IMHO, this should make Langchain much easier and less chaotic to use.
Re: Native JSON Output from GPT-4
#124Earlier quoted context omitted.
> fuzzy logic Yes and no. While the choice of which function to call is dependent on an llm, ultimately, you control the function itself whose output is deterministic. Even today, given an api, people can choose to call or not call based on some factor. We don’t call this fuzzy logic. E.g., people can decide to sell or buy stock through an api based on some internal calculations - doesn’t make the system “fuzzy”.
If you feed that result into another io box you may or may not know if that is the correct answer, which may need some sort of error detection. I think this is going to be majority of the use cases
It’ll be interesting to test APIs which accept user inputs. Depending on how ChatGPT populates the JSON, the API could be required to understand/interpret/respond to lots of variability in inputs.
Re: Native JSON Output from GPT-4
#125Earlier quoted context omitted.
I could not get GPT-4 to reliably not give some sort of text response, even if was just a simple "Sure" followed by the JSON.
Did you try using the API and providing a very clear system message followed by several examples that were pure JSON?
Re: Native JSON Output from GPT-4
#126Re: Native JSON Output from GPT-4
#127Earlier quoted context omitted.
If you feed that result into another io box you may or may not know if that is the correct answer, which may need some sort of error detection. I think this is going to be majority of the use cases
Hm, I see what you mean. Afaict, only the decision to call or not call a function is up to the model (fuzzy). Once it decides to call the function, it generates mostly correct JSON based on your schema and returns that to you as is (not very fuzzy). It’ll be interesting to test APIs which accept user inputs. Depending on how ChatGPT populates the JSON, the API could be required to understand/interpret/respond to lots…
Re: Native JSON Output from GPT-4
#128For those who want to test out the LLM as API idea, we are building a turnkey prompt to API product. Here's Simon's recipe maker deployed in a minute: https://preview.promptjoy.com/apis/1AgCy9 . Public preview to make and test your own API: https://preview.promptjoy.com
Re: Native JSON Output from GPT-4
#129i 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…
Tweeted about it here as well: https://twitter.com/jerryjliu0/status/1668994580396621827?s=...
Re: Native JSON Output from GPT-4
#130Earlier 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.