The value needs a supplied definition
When several plausible values fit a field name, the schema-supplied definition decides which value counts.
What this scenario means
This scenario tests whether a tool follows the schema rule when a document contains more than one plausible value for the same field. It is hard because the right answer is not determined by prominence, and a model must use the supplied definition to choose the correct value. A good system returns the value that matches the schema and ignores the competing one.
What we evaluate
- Whether the returned field value follows the supplied definition when more than one plausible value is present.
- Whether the tool resolves the ambiguity from schema context rather than from the most visible candidate.
- Whether the extracted record contains the schema-selected value and not another plausible value.
Capabilities this scenario exercises
A scenario may exercise one or more capabilities.
Field Extraction
Returns the scalar fields the schema asks for — present, interpreted, derived, absent or differently laid out — correctly typed.
Benchmarks that use this scenario
A scenario has global identity and may be reused across benchmarks.
Structured Document Extraction
Which document extraction platform turns a user-defined schema into correct structured records — across layouts, scans and repeated sets — and is honest about what it could not find?