Can Extend AI use a supplied definition to choose between values that fit the field?
Extend AI selected the consignment reference required by the supplied definition, not the more prominent invoice number. It cited the consignment line on page 1.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Definition overrides the prominent numberPassEvidence
We ran the Calderwood Freight invoice through Extend AI’s extraction screen with a schema defining the requested reference as the consignment reference, not the invoice number.
{ "type": "object", "properties": { "reference_number": { "type": ["string", "null"], "description": "The reference number for this document. For this field, reference number is defined as the reference that identifies the physical consignment of goods being moved. It is NOT the invoice number." } }, "required": ["reference_number"], "additionalProperties": false }
CFS-CN-40821
Returned data: extracted consignment reference
Copied from Output file (JSON), reference_number
Open the whole JSON file ↗| ✓ | Expected: The value the definition selects, not the more prominent candidate.Found: It returned the consignment reference selected by the definition rather than the invoice number. |
Both references fit the field name, and only the supplied schema definition distinguished them; the invoice did not. With that definition supplied, Extend AI returned the consignment reference rather than the more prominent invoice number.
Definition and confidence. The Results panel shows the reference field’s definition beneath its name and a text-recognition confidence score of 0.99 for its value.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Field Extraction → | |
| Scenario | The value needs a supplied definition → | |
| Tool | Extend AI → |
Global scenario definition → · Global capability definition → · Extend AI product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.