AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 19 November 2026

Can Landing AI use a supplied definition to choose the right value?

Landing AI returned the value selected by the supplied definition instead of the more prominent alternative. The invoice number CFS-7710 was the more prominent candidate, and the returned value, CFS-CN-40821, matched the consignment reference.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent

Input · Definition of the schema field consignment_reference: “The consignment reference number (the identifier tied to the physical shipment), NOT the invoice number.”

InputDocument (PDF)
Input PDF: the three-page freight invoice with its invoice number and consignment reference
Open the PDF ↗
What the tool returned
JSONthe whole file · copied line 2
{
  "consignment_reference": "CFS-CN-40821"
}

Returned JSON: the consignment reference CFS-CN-40821 as the field's only value

Copied from Output file 1 (JSON), line 2

Open the JSON file ↗
Output file 2 (JSON)
Extraction metadata: the returned value and the document positions it was drawn from
The tool’s response is printed above, under What the tool returned. Show this file
JSON
{
  "consignment_reference": {
    "value": "CFS-CN-40821",
    "ranges": [
      {
        "end": 225,
        "start": 196
      },
      {
        "end": 1802,
        "start": 1752
      }
    ]
  }
}
Open the JSON file ↗
Expected vs. Found
✓Expected: The value the field's definition selects, the consignment reference, rather than the more prominent invoice number.Found: It returned CFS-CN-40821, the consignment reference, not the invoice number CFS-7710; its metadata points the value to the consignment reference row of the document.
Supporting proof
Proof 1Screenshot
Screenshot: the field's full definition in the schema and the returned value
Open original ↗
Why this result

The field's name fits both the invoice number and the consignment reference, and only its definition rules out the invoice number. Landing AI returned the consignment reference, the value the definition selects, so the result is a Pass.

Also observed in this test case

Invoice number is more prominent. The invoice number CFS-7710 is labelled beside the billing block and repeats in the footer of every page; the consignment reference does not appear in the footers.

Tested by Rugved Nichite · evidence dated 27 October 2026

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.

Software that produced the output
Landing AI
Build or version
DPT-3 Pro (parse model; app version not exposed)
Surface
Web app
Set up before the run
The field had to fit two values in a three-page freight invoice, the invoice number and the consignment reference, with only the field's definition, not the document, saying which one counts.
Schema
version v3 · one string field, with the definition in its description
Tested
27 October 2026 · Rugved Nichite

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
19 November 2026First publishedStructured Document Extraction v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/landing-ai/the-value-needs-a-supplied-definition · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-19

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.

Input · Document (PDF) ↗application/pdf · 118 KB
Output file 1 (JSON) ↗text/plain; charset=utf-8 · 0 KB
Proof 1 · Screenshot ↗image/png · 39 KB
Output file 2 (JSON) ↗text/plain; charset=utf-8 · 0 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1bcc6c7b945956c5b6f5a87d223ed3d578a62aa2c56c5fc1e3abedb4cc4de72e
Output file 1 (JSON)f780883a391216152442184f1c7cf12a41f219ffe0b5b1043f42045d6a852d88
Proof 1 · Screenshota9d5afb44d5b9cfaf449e14d71ece5d5a01b0188a735b40eab4f98108660000b
Output file 2 (JSON)018eacd4b8eb4229749177ee30a7347b47b8c24f2a72265f98cc663281985c60