JRD-95 Implement "string contains" approach for jaqket_v2 and jsquad #108
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
mrorii
changed the title
|
Closing this for now as we decided that using the existing F1 instead of string contains is better, in order to penalize very long/redundant answers even if it's correct |
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.
LLMs can sometimes provide correct answers but that may not be an exact match to the ground truth.
In order to account for this, in addition to the existing "exact match" approach, this PR adds a new "string contains" approach. For example, this is done by LINE corporation (https://logmi.jp/tech/articles/325454):