Papers › PubTables-1M: Towards comprehensive table extraction from unstructured documents

PubTables-1M: Towards comprehensive table extraction from unstructured documents

30 Sep 2021CVPR 2022 1arXiv:2110.00061archive 2025-07-28

Brandon Smock, Rohith Pesala, Robin Abraham

Recently, significant progress has been made applying machine learning to the problem of table structure inference and extraction from unstructured documents. However, one of the greatest challenges remains the creation of datasets with complete, unambiguous ground truth at scale. To address this, we develop a new, more comprehensive dataset for table extraction, called PubTables-1M. PubTables-1M contains nearly one million tables from scientific articles, supports multiple input modalities, and contains detailed header and location information for table structures, making it useful for a wide variety of modeling approaches. It also addresses a significant source of ground truth inconsistency observed in prior datasets called oversegmentation, using a novel canonicalization procedure. We demonstrate that these improvements lead to a significant increase in training performance and a more reliable estimate of model performance at evaluation for table structure recognition. Further, we show that transformer-based object detection models trained on PubTables-1M produce excellent results for all three tasks of detection, structure recognition, and functional analysis without the need for any special customization for these tasks. Data and code will be released at https://github.com/microsoft/table-transformer.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 13 code samples harvested from 2 repositories linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 3 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 3 samples from 1 repository, 3 ran (1 with no instrument failure; 2 where Syntology's instrument failed); community (archive-listed): 10 samples from 1 repository, 8 ran (8 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

microsoft/table-transformer officialmentioned in papermentioned on GitHubpytorchSyntology: 3 samples, 3 ran (2 instrument-failed) · 0 unverified report
phamquiluan/table-transformer pytorchMITSyntology: 10 samples, 8 ran (0 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 3 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run
6ran
2unverified

Licence: 10 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

microsoft/table-transformer official repository 3 samples, 3 ran (2 instrument-failed) · 0 unverified
box_cxcywh_to_xyxy in 60 papers src/inference.py ran · honoured contract fingerprinted MIT (permissive) · 52d4b812bdc17687 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
get_class_map src/inference.py ran · our draft was wrong MIT (permissive) · 0342a5d56baf82fb · report fixture: signature data_type:str/0/str · returned dict · level recorded 2026-09-22
rescale_bboxes in 13 papers src/inference.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · 44195a5621bcf750 · report fixture: signature out_bbox:Tensor/2/float, size:tuple/1/int · returned Tensor · level recorded 2026-09-22
phamquiluan/table-transformer community (archive-listed) 10 samples, 8 ran (0 instrument-failed) · 2 unverified
align_1d src/grits.py ran MIT recorded; this copy not marked cleared · pointer only · 8ac9e5fec2aa104d · report fixture: signature sequence1:list/1/str, sequence2:list/1/str, reward_function:callable/0/?, return_alignment:bool/0/bool · returned tuple · level recorded 2026-09-24
apply_class_thresholds src/eval_utils.py ran MIT recorded; this copy not marked cleared · pointer only · ba4693e812106154 · report fixture: signature bboxes:list/1/Tensor, labels:list/1/int, scores:list/1/float, class_names:list/1/str, class_thresholds:dict/0/? · returned tuple · level recorded 2026-09-24
apply_threshold src/eval_utils.py ran MIT recorded; this copy not marked cleared · pointer only · 4877ebf4c4df63a4 · report fixture: signature objects:list/1/dict, threshold:float/0/float · returned list · level recorded 2026-09-24
box_cxcywh_to_xyxy in 60 papers src/transforms.py ran · honoured contract fingerprinted MIT recorded; this copy not marked cleared · pointer only · e0a06ded5d4f6c3c · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
box_xyxy_to_cxcywh in 37 papers src/transforms.py ran · honoured contract fingerprinted MIT recorded; this copy not marked cleared · pointer only · 031b02fb990284ba · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
load_json in 344 papers core.py ran MIT recorded; this copy not marked cleared · pointer only · 7c2ef30ca5a59095 · report fixture: signature json_path:str/0/str · returned dict · level recorded 2026-09-24
read_pascal_voc src/table_datasets.py ran MIT recorded; this copy not marked cleared · pointer only · e914fd7c0331c5f1 · report fixture: signature xml_file:str/0/str, class_map:dict/0/? · returned tuple · level recorded 2026-09-24
transpose in 53 papers
census: 6 implementations from 13 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
src/grits.py ran MIT recorded; this copy not marked cleared · pointer only · 1503ee81768a3749 · report fixture: signature matrix:list/1/list · returned list · level recorded 2026-09-24
build_transformer in 62 papers detr/models/transformer.py unverified MIT recorded; this copy not marked cleared · pointer only · 302ec916d91b12a8 · report
crop_around_bbox_coco src/table_datasets.py unverified MIT recorded; this copy not marked cleared · pointer only · 3cac9717d8564e2d · report

Tasks

ArticlesObject DetectionTable DetectionTable ExtractionTable Functional AnalysisTable Recognitionobject-detection

Datasets

Introduced by this paper, per the archive.

PubTables-1M

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEConvolutionDense ConnectionsDetrDropoutFeedforward NetworkLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections