generated from opentensor/bittensor-subnet-template
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Features/multiturn conversation #217
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pre-staging
v2.0 [WIP]
Pre staging
Version 2.1.0
…e QA with 50% each turn
…opentensor/prompting into features/multiturn-conversation
p-ferreira
approved these changes
Apr 30, 2024
bkb2135
approved these changes
Apr 30, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds multi-turn conversation capabilities to the validator. This is important for the following reasons:
Overview:
QuestionAnsweringTask
to create followup questions, with a dedicated followup prompt.Followup prompt
Several iterations of prompt engineering were carried out. Each was manually inspected, analyzed for obvious artefacts (QG+QA, length) and run through a battery of gpt4 evals.
A total of 6 iterations of prompt engineering were carried out. After refinement, the followup prompt we now appears to produce good, continuous conversations.
Reference answers, as judged by rewards distributions on tracked experiments. The plots show no clear deterioration in rewards with conversation turn, which indicates that the prompts are stable.


GPT-4 evals
The plots below show the quality of the followup questions based on GPT4 as a judge
