Earlier quoted context omitted.
It's about 0.2 cents right? It's hard for something you interact with manually to provide positive value less than 0.2c.
That's for the non-finetuned GPT3.5turbo model. Finetuned is 1.2cents/1k in and 1.6cents/1k out. So it'll likely be closer to 2cents depending on what you're doing. I'm not saying it's not useful, at 2c per query you have to be more "purposeful" as they could certainly add up depending on how you use it compared to 0.2c.
Fine-tuning GPT-3.5-turbo for natural language to SQL
21–30 of 77 posts
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#22Are you planning on submitting this model to be evaluated against the Spider holdout set? Also, wondering if anyone has found research on the inverse of this approach to the problem, i.e., instead of training the model to understand the data, you improve the data to be more understandable to a model? This seems more promising when you are looking at enterprise use cases without much training data. Spider seems like q…
Yes, we have already submitted the model for evaluation on the Spider holdout test set. While your suggestion is certainly intriguing, implementing a universal solution could be quite challenging, as it would heavily depend on the specifics of the dataset.
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#23The cost per question seems super high. I can't even think of an API where a single call would cost $1cent. You better have a good pricing model to follow up on this.
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#24Spider isn't anything like the queries that analysts and data scientists write against DBs. I don't think it even has many joins. Do you not have access to a more realistic training set?
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#25Instead of going for generative, few-shot models, I am starting to look at the other end of the spectrum: Binary classification into deterministic query building.
With ChatGPT, you cannot realistically explain why you got some output in a way that anyone other than an AI/ML expert would find satisfying. With binary classifiers, you can precisely explain how some input resulted in some output in terms that a business person could easily digest - "You mentioned this table so it assumed you wanted to constrain on XYZ. Here's the trace from the classifiers...".
I've proposed a few schemes where you define groups of classifiers for each SQL building concern - Which tables are involved, which columns, is a join or aggregate implied, general context of business use, etc. Clearly, there are holes with this scheme, but in our domain we could plausibly fine-tune our humans to be a little bit more verbose in their use of the automagic SQL vending machine. Several hours spent training humans is probably a lot cheaper & easier than getting ChatGPT, et. al. to consistently play by our rules.
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#26Spider isn't anything like the queries that analysts and data scientists write against DBs. I don't think it even has many joins. Do you not have access to a more realistic training set?
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#27We've been chasing this rabbit since the beginning. It currently seems to be uncatchable for the use cases that would be most valuable to us - writing complex queries we've never seen before. Our use case seems to confound any notion of training or fine-tuning, since the cases we need the most help with are also the ones we have the fewest examples of. Instead of going for generative, few-shot models, I am starting t…
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#28See the following for more info:
https://yale-lily.github.io/spider https://github.com/taoyds/spider/tree/master/evaluation_exam...
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#29Spider isn't anything like the queries that analysts and data scientists write against DBs. I don't think it even has many joins. Do you not have access to a more realistic training set?
Re: Fine-tuning GPT-3.5-turbo for natural language to SQL
#30We've been chasing this rabbit since the beginning. It currently seems to be uncatchable for the use cases that would be most valuable to us - writing complex queries we've never seen before. Our use case seems to confound any notion of training or fine-tuning, since the cases we need the most help with are also the ones we have the fewest examples of. Instead of going for generative, few-shot models, I am starting t…