Ilmu Komputer & AI editorial
Beyond Tables: Doc2DB-Bench for Relationally Faithful Document-to-Database Construction
The core problem
Innovation
The benchmark is constructed through a controllable DB-to-Doc synthesis pipeline. This pipeline begins with a relational database instance and generates a long, heterogeneous document that encodes the same information in natural language. The synthesis is organized by a taxonomy of intra-table extraction and inter-table reasoning, ensuring coverage of both local field-level extraction and global relational inference. The generated documents undergo authenticity verification, demonstrating that they are indistinguishable from real-world references. The benchmark comprises 203 long-document instances across 42 schemas and seven domain groups, yielding 117 entity tables, 132 relationship tables, 7,341 rows, and 41,935 cells. Formally, let a document be generated from a database instance
Why it matters
The key insight of Doc2DB-Bench is that document understanding should be evaluated as database construction rather than field extraction. This reframing addresses critical limitations of Document-to-Table benchmarks: flattening evidence into single tables can duplicate entities, obscure many-to-many relationships, create sparse records, and avoid testing whether extracted facts form a valid database instance. In domains such as finance, healthcare, education, transportation, and enterprise operations, downstream workflows rely on normalized schemas, entity identities, keys, cross-table relationships, and integrity constraints for analytics, compliance, auditing, and SQL-backed decision making. Therefore, evaluating document understanding as database construction is essential for reliable, auditable, and relationally faithful LLM-based data systems. The benchmark's taxonomy of intra-table extraction and inter-table reasoning provides a principled way to measure progress. The authenticity verification ensures that the generated documents are realistic, making the benchmark a challenging testbed. The public availability of the benchmark at https://github.com/SetonLiang/Doc2DB-Bench supports reproducible research. The following Mermaid diagram illustrates the DB-to-Doc synthesis and evaluation pipeline:
This pipeline highlights the inverse problem: from document to database, with evaluation focused on relational faithfulness rather than isolated field extraction.
Who should read this
Opening member contentโฆ