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

Can Nanonets extract a repeated set of records?

Nanonets kept the repeated invoice items separate and preserved their associated values. The output contained three objects for the source table's three rows.

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.

Repeated set with correct associationPassEvidence
What we sent

“Extract the following fields from this document and return the result as JSON: invoice_number, bill_to, site, hire_period, subtotal, tax, total_due, and line_items (an array of objects with description, quantity, unit_price, amount).”

InputDocument (PDF)
Input PDF: the plant-hire invoice with three line items on one page
Open the PDF ↗
What the tool returned
JSONthe whole file · copied lines 6–24
{
  "invoice_number": "TPH-3301",
  "bill_to": "Oakbridge Construction Ltd\nSite Office, Oakbridge Depot Extension\nDarrowby DL4 7HN",
  "site": "Oakbridge Depot Extension",
  "hire_period": "03 Mar - 10 Mar 2026",
  "line_items": [
    {
      "description": "Telehandler, 4-tonne, weekly hire",
      "quantity": "1",
      "unit_price": "£850.00",
      "amount": "£850.00"
    },
    {
      "description": "Generator, 20kVA, weekly hire",
      "quantity": "2",
      "unit_price": "£210.00",
      "amount": "£420.00"
    },
    {
      "description": "Site fencing, per 10m panel, weekly",
      "quantity": "8",
      "unit_price": "£24.00",
      "amount": "£192.00"
    }
  ],
  "subtotal": "£1,462.00",
  "tax": "£292.40",
  "total_due": "£1,754.40"
}

Returned JSON: three line items with their descriptions, quantities, unit prices and amounts

Copied from Output file (JSON), lines 6–24

Open the JSON file ↗
Expected vs. Found
✓Expected: Return all three line items with the source values attached to the correct item, without omissions or duplicates.Found: It returned three line items for the invoice's three rows, with no omissions or duplicates; each description, quantity, unit price and amount stayed with its corresponding item.
Supporting proof
Proof 1Screenshot
Result screen: the expanded table showing the three extracted line items
Open original ↗
Proof 2Screenshot
Task screen: the full extraction request and attached invoice
Open original ↗
Why this result

The task required keeping each item's values together. The returned array reproduced the invoice's three rows, and each quantity multiplied by its unit price equalled that item's amount, confirming the associations.

Tested by Rugved Nichite · evidence dated 9 September 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 input was a plant-hire invoice with three plainly delimited line items on one page. The request asked for an array containing each item's description, quantity, unit price and amount.
Tested
9 September 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
CapabilityNested & Repeated Fields →
ScenarioA repeated set of records →
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
13 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/a-repeated-set-of-records · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-13

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 · 78 KB
Output file (JSON) ↗application/json · 1 KB
Proof 1 · Screenshot ↗image/png · 171 KB
Proof 2 · Screenshot ↗image/png · 186 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)fdcf03ac5ee53b083da58166f17fd41e7c72de79a9f3a3f6b67daa1360ddbca9
Output file (JSON)e36c87956e8ceb4c66af40a4a15b640538edc76a7aa603490ad9cf23aff8a15d
Proof 1 · Screenshot1de5d9aa0230ae0960f8abc134d25c6829407c585985e6b1958d8b8f05d4382a
Proof 2 · Screenshot0b18d879842d87ef49ad2f5225c969f6820d5b44b6d84886151b240d7d775d9e