Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LLM response parsing error #5

Open
h-croser opened this issue Jan 10, 2024 · 2 comments
Open

LLM response parsing error #5

h-croser opened this issue Jan 10, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@h-croser
Copy link
Contributor

Description

Sometimes the LLM responds with a JSON object called "answers". When this occurs, the results parser fails to parse the results for the given batch.

Replication

The bug was identified using this source file - 19_clauses.txt
The prompts and responses containing the error can be found here - results57.zip
In the subfolder 'prompts_responses' the response labelled '8fGaiWfHAL0ntiOSW5sAJ3DZZbOiC' can be seen to be in a different format to the other responses. Additionally, the offending response is the only response with an associated txt file (might be a hint on the failure point?)

Unfortunately, I was unable to replicate the bug using the same file.

@h-croser h-croser added the bug Something isn't working label Jan 10, 2024
@sebhaan
Copy link
Contributor

sebhaan commented Jan 29, 2024

that's what's very likely causing it: The output include the json object "answer" because the examples in the prompt are structured along "input\n ...." and "answer\n". This likely just needs a change in parsing the examples in the prompt. Alternative is to read the asnwer json object of default method fails.

@sebhaan
Copy link
Contributor

sebhaan commented Feb 1, 2024

changed prompt instructions (commit 4c9152d), which might solve the problem. Report here if response still fails to provide correct format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants