Repository navigation
Document off-schema key scoring in score_root - #95
Merged
Merged
Conversation
Value F1 is defined over schema keys. State that an off-schema root key counts as one opaque predicted cell and nested off-schema keys are ignored, so readers can interpret precision (#94).
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.
What
Rewrites the comment in
score_rootto state how off-schema keys are scored.Why
#94 asked whether one cell per off-schema key is intended. It is: value F1 is defined over schema keys. The comment now says so, including that nested off-schema keys are ignored.
Changes
src/extract_bench/evaluation/metrics/extract/unified_evidence_metric.py: comment only.Testing
Comment-only change; no behavior or score change.
ruff checkandruff format --checkpass.Refs #94