AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
superseded result

This is the result as it was published on 23 October 2026. A newer result replaced it on 27 October 2026; this page is kept so that anything that cited it still resolves. Read the current result →

Graded 11 October 2026

Does FutureSmart Document Intelligence keep a non-member out of the extracted set?

FutureSmart Document Intelligence passed this non-member scenario. It kept the five genuine rows, omitted the Total row, showed the same five items on screen, and treated the 1,982.00 GBP total as document-level information.

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 counts this row.

Total row is not a memberPassEvidence
What we sent
InputDocument (PDF)
Invoice page with five items and a Total row
Open the PDF ↗
What the tool returned
JSON
{
  "summary": "This document is an invoice issued by Meridian Retail Group to Coppergate Wholesale Ltd for the supply of retail fixtures and store equipment. It details five specific items provided, including shelving units, checkout counters, and security equipment, totaling 1,982.00 GBP.",
  "document_type": "invoice",
  "line_items": [
    {
      "amount": 504,
      "quantity": 6,
      "unit_price": 84,
      "description": "Retail Shelving Unit - Steel, 5-Tier"
    },
    {
      "amount": 620,
      "quantity": 2,
      "unit_price": 310,
      "description": "Checkout Counter - Laminate Top"
    },
    {
      "amount": 182,
      "quantity": 4,
      "unit_price": 45.5,
      "description": "Security Tag Deactivator - Handheld"
    },
    {
      "amount": 486,
      "quantity": 3,
      "unit_price": 162,
      "description": "Price Label Printer - Thermal"
    },
    {
      "amount": 190,
      "quantity": 5,
      "unit_price": 38,
      "description": "Shopping Basket - 20L, Set of 10"
    }
  ]
}

Extraction JSON with five line items

Copied from Output file (JSON), lines 1–36

Open the JSON file ↗
Expected vs. Found
✓Expected: Only the genuine rows belong in the output; the lookalike row must be left out.Found: Five complete line items were returned, and the Total row was absent.
Supporting proof
Proof 1Screenshot
Metadata screen with five line-item cards
The tool’s response is printed above, under What the tool returned. Show this screenshotOpen original ↗
Why this result

It is a Pass, not a fail: the output contains the five real rows and excludes Total, and the screen shows the same five items.

Also observed on this row

Total in summary. The product also placed the 1,982.00 GBP total in the summary, not in the line-items list.

Tested by Rugved nichite
Limitations of this result

The screenshot cuts off below Item 5, so it does not show any later page content.

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
FutureSmart Document Intelligence
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
A matching invoice-style table had to include one same-shaped lookalike row, clearly labelled as not a member; the product was run to extract only the real members.
Extraction schema
line_items
Tested
By 19 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 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.

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
23 October 2026First publishedStructured Document Extraction v1
27 October 2026Updated — the page was revised
The result is unchanged: 1 pass · 0 fail. The earlier result stays readable. Read the earlier result →

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/futuresmart-document-intelligence/the-set-contains-a-non-record · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-11

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

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)791590c9d422110ebebf3c1e434eebac20aff3c6728024693becc870818c26d8
Output file (JSON)34ec11c50eb6ad43d8fd3d555d782b23084d116300fe5675ddc093fe353fd540
Proof 1 · Screenshotf8f6c83a0cc4f90dddf9457e5dbf55549f5f826694f713388a39f9d2d3b36502