Scenario definition · S31

A simple, clearly formatted table

A simple, clearly formatted table is provided for processing.

What this scenario means

This scenario checks whether a system preserves table structure when the layout is straightforward. A good system keeps rows, columns, headers and value-to-header links intact, so the table remains usable instead of becoming flattened text, shifted cells or a broken grid.

What we evaluate

  • Whether the rows and columns remain aligned after processing.
  • Whether each value stays under the correct header.
  • Whether the output still reads as a table rather than a flattened or split block of text.
◌Test-case detail. Exact wording, inputs, fixture state, expected output and detailed grading remain at the test-case level and may be withheld while the benchmark version is active. The scenario and its evaluation intent are public.

Capabilities this scenario exercises

A scenario may exercise one or more capabilities.

Capability · via another benchmark

Data Ingestion

The knowledge in the files you hand over actually becomes reachable — and the service tells you when it didn't. Graded with the retrieval side held trivially easy (a query in the source's own wording over a small corpus), so a failure is attributable to ingestion rather than to search.

Capability

Table Extraction

Relational data — values whose meaning lives in row/column association; the one type whose partial failure yields confidently wrong downstream answers rather than gaps

Benchmarks that use this scenario

A scenario has global identity and may be reused across benchmarks.

Benchmark

Managed RAG

Which managed RAG service turns a folder of private documents into a query API that finds the right passage, answers only from what it retrieved, cites the source that actually supports the claim — and keeps up when the source changes?

View tool results on this scenario →

A simple, clearly formatted table — Scenario definition | AI Demos