#GPT3 & Live Data

17 messages · Page 1 of 1 (latest)

wheat musk
#

GPT-3 does not have the ability to access live data.

#

GPT3 & Live Data

drifting heron
#

@wheat musk , thanks, so there would need to be something in between, like for example process a request to generate some sort of formatted query then feed that to a secondary system?

wheat musk
#

hmmm. It really depends on what you're trying to do. It's not totally clear based on what you've written. Can you give one example of an end-to-end flow?

drifting heron
#

sure, let's say I want to ask about the state of a number of live tracked sensors that all generate real time data

#

but I don't want the person asking to be writing a query to pull data from a database or anything like that

#

"I want to know which sensors are operating outside the norm or are experiencing unusual activity"

#

then we have a database with live sensor data, that has this information, that we want to pull

#

as you mentioned, there's no way for GPT3 to know anything about this data, but it could generate a query to pull the data and then we could output this separately based on the query?

wheat musk
#

interesting, good use case....
GPT-3 can only answer questions about what it has knowledge of. There isn't a way to feed in live data.

It sounds like what you really want is to be able to query a database without the user having to use a database query language. Correct?

drifting heron
#

something along those lines. And I understand reading the docs that this would be more of a fine-tuning type of scenario, but essentially it would be a use-case specific query with a specific format to be interpreted by a secondary system given the limitation of access to that live data

wheat musk
#

Yes I think you are right. I'm imagining you could do this, though it would be a bit ham fisted and potentially prone to error (unless you fine tune a model):

  1. User types in natural language what they want to know.
  2. You design a backend that will take that and merge in some information about the database (eg. column names, row names)
  3. The back end sends this to GPT requesting an appropriate query for the database (eg. SQL)
  4. GPT returns the result to your back end
  5. Your back end submits the query
  6. Your back end returns the answer to the database query for the user
drifting heron
#

I appreciate you taking the time to answer this.

wheat musk
#

You're welcome. There may be better ways to do this! There are many ways to skin a cat... But that is what comes to mind for me.

drifting heron
#

I'll keep digging through the docs and see what comes up, Thanks again, really appreciated

wheat musk
#

If you end up designing this or come up with a better system please share here! I'd love to see how it works or if there is a better way to do this 🙂