Can Landing AI answer a document fact that is not in the extracted fields?
Landing AI passed this scenario. It answered the technician question with Renata Kowalski and showed clickable references to the receipt’s page text, while the receipt itself prints that name. Chat is experimental, works on one file at a time, and has no API, so the result is scoped to the web app.
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 counts this row.
Answer outside the schema, attributedPassEvidence
“Who was the technician on the receipt?”
The technician on the receipt was Renata Kowalski.
Transcribed from Proof 2 · Screenshot
| ✓ | Expected: It should either say the fact is not in the extracted data or answer and say it came from the document.Found: It answered with Renata Kowalski and showed clickable page-text references, rather than presenting the name as an extracted field. |
Chat tab, file Baseline_receipt, new chat Question: Who was the technician on the receipt? Answer: The technician on the receipt was Renata Kowalski. Visual reference for the answer (clickable): Page 1.text | TECHNICIAN ; Page 1.text | Renata Kowalski
The question was about a page fact outside the extracted fields. Chat answered with the technician’s name and tied it to page text, while the receipt itself shows that name.
Clickable attribution. The product shows its attribution as clickable citation chips rather than as a sentence.
Chat scope. Chat is experimental, works on one file at a time, and has no API; this result applies to the web app.
The screenshot does not show the extraction schema.
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 row says which 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 row 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 | Querying → | |
| Scenario | The answer was never in the schema → | |
| Tool | Landing AI → |
Global scenario definition → · Global capability definition → · Landing 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.