Add claim-support benchmark for transcript-grounded scoring#4478
Closed
dpaul0501 wants to merge 1 commit into
Closed
Add claim-support benchmark for transcript-grounded scoring#4478dpaul0501 wants to merge 1 commit into
dpaul0501 wants to merge 1 commit into
Conversation
Collaborator
|
Duplicate of #4166 |
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
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.
This PR contains:
What is the current behavior? (You can also link to an open issue here)
claim_support()is available as a transcript-aware model-graded scorer, but it only evaluates the final claim in a single pass.What is the new behavior?
This PR adds an optional atomic-claim verification flow for
claim_support()viadecompose_claims=True.It also adds:
claim_support()appears in the built-in scorer listDoes this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking change.
claim_support()keeps its existing behavior by default. Existing users do not need to change anything unless they want the new atomic-claim mode, in which case they can opt intodecompose_claims=True.Other information:
This is meant to make claim verification more robust for agent and security-trace evaluations, especially when answers contain multiple facts bundled into one response.