Papers › HRDoc: Dataset and Baseline Method Toward Hierarchical Reconstruction of Document Structures
HRDoc: Dataset and Baseline Method Toward Hierarchical Reconstruction of Document Structures
Jiefeng Ma, Jun Du, Pengfei Hu, Zhenrong Zhang, Jianshu Zhang, Huihui Zhu, Cong Liu
The problem of document structure reconstruction refers to converting digital or scanned documents into corresponding semantic structures. Most existing works mainly focus on splitting the boundary of each element in a single document page, neglecting the reconstruction of semantic structure in multi-page documents. This paper introduces hierarchical reconstruction of document structures as a novel task suitable for NLP and CV fields. To better evaluate the system performance on the new task, we built a large-scale dataset named HRDoc, which consists of 2,500 multi-page documents with nearly 2 million semantic units. Every document in HRDoc has line-level annotations including categories and relations obtained from rule-based extractors and human annotators. Moreover, we proposed an encoder-decoder-based hierarchical document structure parsing system (DSPS) to tackle this problem. By adopting a multi-modal bidirectional encoder and a structure-aware GRU decoder with soft-mask operation, the DSPS model surpass the baseline method by a large margin. All scripts and datasets will be made publicly available at https://github.com/jfma-USTC/HRDoc.
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):
get_harvested_code_for_paper(arxiv_id="2303.13839")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2303.13839", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2303.13839")
Code
Syntology 14 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 3 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 14 samples from 1 repository, 12 ran (10 with no instrument failure; 2 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.
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
14 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 3 honoured, 0 violated, 7 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.
Licence: 14 of the 14 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 jfma-ustc/hrdoc. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.
fbaaa371b4ebbafd · report
fixture: signature feats:Tensor/3/float, feats_mask:Tensor/2/float · returned Tensor · level recorded 2026-09-24 0261882ecf3d1c25 · report
fixture: signature inputs:Tensor/3/float, masks:Tensor/2/float, hidden:NoneType/0/? · returned Tensor · level recorded 2026-09-24 b7f63470f062747e · report
fixture: signature lines_box:list/1/Tensor, img_sizes:list/1/Tensor · returned list · level recorded 2026-09-24 1a652039016eccb4 · report
fixture: signature input:Tensor/4/float, input_mask:Tensor/4/float · returned tuple · level recorded 2026-09-24 59f958c41892d782 · report
fixture: signature feats:Tensor/4/float, lines_box:list/1/Tensor · returned Tensor · level recorded 2026-09-22 f350d387d051c671 · report
fixture: returned list · level recorded 2026-09-24 540e50267a8213fe · report
fixture: signature v_feature:Tensor/2/float, s_feature:Tensor/2/float, p_feature:Tensor/2/float · returned list · level recorded 2026-09-22 71a97abe47fc54dc · report
fixture: signature feats:list/1/Tensor · returned tuple · level recorded 2026-09-22 c8c6a98626ee0e88 · report
fixture: signature tokens_ids:list/1/Tensor, device:str/0/str, dtype:dtype/0/? · returned tuple · level recorded 2026-09-22 49abff9073550b42 · report
fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, dilation:int/0/int · returned Conv2d · level recorded 2026-09-22 0e7b2457e7e96b9a · report
fixture: signature lines_box:list/1/Tensor · returned Tensor · level recorded 2026-09-22 59c421bb1bb38e71 · report
fixture: signature tokenizer:callable/0/?, token_batch:list/1/list, max_token:int/0/int · returned tuple · level recorded 2026-09-22 census: 6 implementations from 6 papers, 5 distinct outputs on one shared input end2end_system/strcut_recover/libs/model/encoder.py unverified no licence file found · pointer only ·
46cf9697f6679bb5 · report
ad74f969c400615a · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for DSPS (graph method: DSPS). 15 bricks; individually on a fixture: 13 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 3 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.
- Encoder entry · level 0 · unverified ·
ad74f969c400615a - BasicBlock helper · level 0 · unverified ·
46cf9697f6679bb5 - LstmFusion model · level 1 · ran ·
fbaaa371b4ebbafd - PosFeat helper · level 1 · ran ·
b7f63470f062747e - ResNet model · level 1 · ran ·
1a652039016eccb4 - RoiFeatExtractor helper · level 1 · ran ·
59f958c41892d782 - SemanticsFeatExtractor model · level 1 · ran ·
f350d387d051c671 - VSFD helper · level 1 · ran ·
540e50267a8213fe - align_feats helper · level 1 · ran · our draft was wrong ·
71a97abe47fc54dc - conv3x3 helper · level 1 · ran · our draft was wrong ·
49abff9073550b42 - PadRNN helper · level 1 · ran ·
0261882ecf3d1c25 - conv1x1 helper · level 1 · ran · our draft was wrong ·
158bf4c3a5f11f04 - convert_to_roi_format helper · level 1 · ran · honoured contract ·
0e7b2457e7e96b9a - tokenize helper · level 1 · ran · honoured contract ·
59c421bb1bb38e71 - align_tokens helper · level 1 · ran · honoured contract ·
c8c6a98626ee0e88
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2303.13839") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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