modify prompts to improve entity and attribute value handling #31
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
|
@deepnayak - just the beginnings of some ideas for how to approach modifying the prompts to help with attribute conditions |
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.
Exploring ideas to improve attribute condition setting.
Using "none" rather than "required" as a condition value seems to help a little in the way the model interprets the request.
Also trying out the idea of masking entities in the query before passing them to the attribute steps. Currently there is a tendency for entities to be interpreted as values so masking them may help reduce false condition setting. Haven't followed through with this but including the modified entity prompt as a reference in case it seems worth pursuing.