-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add two criteria based direct llm judges #1527
Conversation
Signed-off-by: lilacheden <[email protected]>
"option_map": option_map, | ||
} | ||
) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Criteria should be added here as catalog entries:
https://www.unitxt.ai/en/latest/catalog/catalog.metrics.llm_as_judge.direct.criterias.__dir__.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So they can be reused.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yoavkatz - ok, added the criteria to the catalog
Signed-off-by: lilacheden <[email protected]>
) | ||
add_to_catalog( | ||
adherence_metric, | ||
f"metrics.llm_as_judge.direct.criteria_judges.llama_3_3_70b_instruct_{adherence_criteria.name}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since these metrics require specific fields (e.g. "question" or "reference_answer"). I think it will be simpler for the users to understand when to use them, by they are under the task "metrics.rag.response_generation.adherence.llama_3_3_70b_instruct_judge"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Signed-off-by: lilacheden <[email protected]>
No description provided.