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

Does Nanonets leave a missing field blank without inventing a source?

Nanonets left the absent loyalty membership number empty without inventing a source. It explicitly reported that the document did not contain the number.

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.

Absent field returns an honest nullPassEvidence
What we sent

Input 1 · Initial receipt extraction: “Extract the following fields from this document and return the result as JSON: receipt_number, subtotal, tax, total_due.”

Input 2 · Absent-field follow-up: “What is the customer's loyalty membership number on this receipt? Also, tell me what page or location this value came from.”

InputDocument (PDF)
Input PDF: service receipt with no loyalty membership number
Open the PDF ↗
What the tool returned

Loyalty membership extraction table Loyalty Membership Number —; Page Number 1; Location Loyalty membership number not found on the document. Reply about the absent number No further document processing is needed. The requested receipt fields were extracted, and the follow-up search confirmed that no loyalty membership number appears on page 1. The next step is simply to report that finding to the user, unless they want a different field or a recheck of another document.

Transcribed from Proof 1 · Screenshot

Everything the tool returned, in order (6)
  1. Receipt extraction progress

    Planned for 23s · Extracting data from your document...

  2. Initial receipt extraction table

    Receipt Number RHS-70234; Subtotal $85.00; Tax $5.10; Total Due $90.10

  3. Initial extraction reply

    Extracted the requested receipt fields and returned them as JSON: receipt_number "RHS-70234", subtotal "$85.00", tax "$5.10", and total_due "$90.10".

  4. Follow-up extraction progress

    Planned for 19s · Extracting data from your document...

  5. Loyalty membership extraction table

    Loyalty Membership Number —; Page Number 1; Location Loyalty membership number not found on the document.

  6. Reply about the absent number

    No further document processing is needed. The requested receipt fields were extracted, and the follow-up search confirmed that no loyalty membership number appears on page 1. The next step is simply to report that finding to the user, unless they want a different field or a recheck of another document.

Output file (JSON)
Returned JSON: empty loyalty membership number and an absence note
JSON
{
  "loyalty_membership_number": null,
  "page_number": 1,
  "location": "Loyalty membership number not found on the document."
}
Open the JSON file ↗
Key momentslines 1–5
Expected vs. Found
✓Expected: Return null for the absent fact, without inventing a value or attaching a source pointer to an invented value.Found: The table showed a dash and JSON returned null. Of 1 request, 0 invented a value; 0 invented values received source pointers.
Supporting proof
Proof 1Screenshot
Task screenshot: initial receipt extraction, loyalty-number follow-up and empty result
Open original ↗
Why this result

The receipt contains no loyalty membership number, so returning null meets the requirement not to invent one. Page 1 identifies the page searched, not evidence for a value; no invented location was supplied.

Also observed in this test case

Receipt fields extracted first. Before the loyalty-number question, Nanonets correctly extracted the receipt number, subtotal, tax and total due, showing that it had read the document in full.

Tested by Rugved Nichite · evidence dated 26 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
Nanonets
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The unchanged service receipt was required as input, with an added request for the customer's loyalty membership number—a fact the receipt does not contain or imply.
Tested
26 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.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityField Extraction →
CapabilitySource Grounding →
ScenarioThe field is absent →
ToolNanonets →

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
17 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/nanonets/the-field-is-absent · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-16

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 · 7 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 0 KB
Proof 1 · Screenshot ↗image/png · 169 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1f464ae863aadb1682805b8ee3fdd8b368a2ddd4e0f602e1cb194640b9253302
Output file (JSON)a329aa0e7dcc1677bf5a232796a3cda1f9c37a0bf763cb342e2706dd5a230967
Proof 1 · Screenshot4d3809c3b7909e83d42d859874a65e44893bdd1d817662b8fdb8613740366da5