[low-priority] mmlu_pro: Allow using LLM-as-judge as parser#101
Open
[low-priority] mmlu_pro: Allow using LLM-as-judge as parser#101
Conversation
tomtseng
force-pushed
the
tomtseng/mmlu-pro-llm-judge-impl
branch
from
60d56b7 to
8cb0e39
Compare
tomtseng
force-pushed
the
tomtseng/mmlu-pro-llm-judge-impl
branch
from
8cb0e39 to
77eaa35
Compare
tomtseng
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes
In PR #99 we found that LLM-as-a-judge for MMLU-Pro grading works better than the regex parser, though it doesn't change our top-line results much. This PR edits MMLU-Pro to allow configuring MMLU-Pro to use LLM-as-a-judge grading (as opposed to #99 which invokes the LLM-as-a-judge post-hoc), but still defaults to the regex parser.
Testing
new unit tests. I haven't tried running the code fully end-to-end