mirror of
https://github.com/kennethreitz/instructor.git
synced 2026-06-05 22:50:18 +00:00
8449543376
* maybe * everything
109 lines
3.6 KiB
Markdown
109 lines
3.6 KiB
Markdown
# Patterns for Extracting Multiple Items
|
|
|
|
A common use case of structured extraction is defining a single schema class and then making another schema to create a list to do multiple extraction
|
|
|
|
```python
|
|
class User(OpenAISchema):
|
|
name: str
|
|
age: int
|
|
|
|
class Users(OpenAISchema):
|
|
users: List[User]
|
|
```
|
|
|
|
Defining a task and creating a list of classes is a common enough pattern that we define a helper function `MultiTask` It procides a function to dynamically create a new class that:
|
|
|
|
1. Dynamic docstrings and class name baed on the task
|
|
2. Helper method to support streaming by collectin function_call tokens until a object back out.
|
|
|
|
## Extracting Tasks using MultiTask
|
|
|
|
By using multitask you get a very convient class with prompts and names automatically defined. You get `from_response` just like any other `OpenAISchema` you're able to extract the list of objects data you want with `MultTask.tasks`.
|
|
|
|
```python hl_lines="13"
|
|
from instructor import OpenAISchema, MultiTask
|
|
|
|
class User(BaseModel):
|
|
name: str
|
|
age: int
|
|
|
|
|
|
MultiUser = MultiTask(User)
|
|
|
|
completion = openai.ChatCompletion.create(
|
|
model="gpt-4-0613",
|
|
temperature=0.1,
|
|
stream=False,
|
|
functions=[MultiUser.openai_schema],
|
|
function_call={"name": MultiUser.openai_schema["name"]},
|
|
messages=[
|
|
{
|
|
"role": "user",
|
|
"content": f"Consider the data below: Jason is 10 and John is 30",
|
|
},
|
|
],
|
|
max_tokens=1000,
|
|
)
|
|
MultiUser.from_response(completion)
|
|
```
|
|
|
|
```sh
|
|
{"tasks": [
|
|
{"name": "Jason", "age": 10},
|
|
{"name": "John", "age": 30}
|
|
]}
|
|
```
|
|
|
|
## Streaming Tasks
|
|
|
|
Since a `MultiTask(T)` is well contrained to `tasks: List[T]` we can make assuptions on how tokens are used and provide a helper method that allows you generate tasks as the the tokens are streamed in
|
|
|
|
!!! tips "Why would we want this?"
|
|
While `gpt-3.5-turbo` is quite fast `gpt-4` will take a while if there are many objects or if each object schema is complex. If 10 entities are created and takes 100ms to complete it would mean that it would take 1 second before we had access to our objects. With streaming you'd get the first object in 100ms a 10x percieved improvement in latency! While this may not make sense for more usecases if we were dynamitcally building UI based on entities, streaming entities 1 by 1 could improve the user experience dramatically.
|
|
|
|
Lets look at an example in action with the same class
|
|
|
|
```python hl_lines="6 26"
|
|
MultiUser = MultiTask(User)
|
|
|
|
completion = openai.ChatCompletion.create(
|
|
model="gpt-4-0613",
|
|
temperature=0.1,
|
|
stream=True,
|
|
functions=[MultiUser.openai_schema],
|
|
function_call={"name": MultiUser.openai_schema["name"]},
|
|
messages=[
|
|
{
|
|
"role": "system",
|
|
"content": "You are a perfect entity extraction system",
|
|
},
|
|
{
|
|
"role": "user",
|
|
"content": (
|
|
f"Consider the data below:\n{input}"
|
|
"Correctly segment it into entitites"
|
|
"Make sure the JSON is correct"
|
|
),
|
|
},
|
|
],
|
|
max_tokens=1000,
|
|
)
|
|
|
|
for user in MultiUser.from_streaming_response(completion):
|
|
assert isinstance(user, User)
|
|
print(user)
|
|
|
|
>>> name="Jason" "age"=10
|
|
>>> name="John" "age"=10
|
|
```
|
|
|
|
!!! usage "How??"
|
|
Consider this incomplete json string.
|
|
|
|
```json
|
|
{"tasks": [{"name": "Jason", "age": 10}
|
|
```
|
|
|
|
Notice how, while this isn't valid json, we know that one complete `User` object was generated so we `yield` that object to be used elsewhere as soon as possible.
|
|
|
|
This streaming is still a prototype, but should work quite well for simple schemas. |