- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The paper extends an existing document dataset (ADOPD 2024) with human-cleaned captions, semantic region labels, and CoT reasoning traces grounded in generic (polygonal) visual regions. The resulting ADOPD 2026 dataset is used to study three document tasks (1) text block grounding (as bounding boxes) and visual entity grounding (as segmentation masks). (2) document region classification (3) visual entity counting. The authors evaluate existing detection and segmentation models. They also introduce an agentic refinement procedure that uses a VLM to tackle fragmented text boxes. For tagging, they compare zero-shot VLMs against a fine-tuned LocateAnything model. They also introduce DocCount, a benchmark of over 400 documents for counting of specific visual categories.
Critical strengths
-
The extension of ADOPD 2024 dataset with addtional annotations (region labels, cleaned captions, and grounded reasoning traces) is a useful contribution.
-
The improvements for text box region refinement obtained through VLM-guided grouping tackles a practical limitation of existing detectors.
Critical weaknesses
-
The proposed extension to ADOPD adds useful annotations, but I am not convinced that it constitutes a sufficiently substantial contribution. Also, recent works such as DocLayout-VL (https://doclayoutvl.github.io/, ECCV 2026) and DoCoG (https://docog-eccv.github.io/, ECCV 2026) already address more challenging and comprehensive formulations of semantic document grounding and grounded reasoning. While these works don't explicitly target counting, they substantially overlap with the central motivation of this paper. To be fair, the proceedings for these works were available recently. I don't consider the absence of experimental comparisons to these concurrent works a weakness. But their existence does diminish the significance of the proposed contribution.
-
The main counting experiments evaluate VLMs for final answer without using the proposed reasoning traces. Therefore, these experiments are not enough to say that the anchor-based reasoning formulation is beneficial.
-
The DocCount benchmark is restricted to only four visual categories and the number of samples is also small.
-
The proposed "agentic self-refinement" appears to be a fixed algorithm of sequential operations involving detector outputs, VLM-based grouping, and geometric checks. It is not clear what makes this procedure agentic. There does not appear to be any autonomous planning, iterative refinement, or adaptive decision-making. Merely involving a VLM in a processing pipeline does not make the approach agentic.
-
The paper claims a unified framework for grounded document reasoning. But the tasks (localization, semantic tagging) and counting experiments are largely independent.
-
The paper discusses challenges with CJK documents. But the analysis does not adequately establish whether these challenges arise from linguistic characteristics, visual complexity, dataset imbalance, or annotation conventions.
-
Most experiments involve evaluating or fine-tuning existing detectors, segmentation models, and VLMs. The reported results are useful as diagnostics, but it is not clear what new methodological insight or generalizable learning principle emerges. In this respect, the work seems closer to a document-analysis benchmark and empirical study than a substantial contribution to machine learning. It also appears more naturally suited to venues such as CVPR, ICDAR, or ACL/EMNLP than ICLR.
Questions for authors
While additional experiments or annotation corrections may address individual issues, it's unlikely to substantially change my overall assessment. I'd be ok if the authors decide to focus on other reviews.
3 comments
W3: DocCount scope.
- Four classes. Brand Logo, Photograph, Table and Chart / Graph were chosen because their definitions are clear and visually separable (§4.3.1), so that every reference count can be checked.
- Size. 442 pages is comparable to several established counting benchmarks in Appendix A.1, such as UCF-QNRF (334), CARPK (459), ShanghaiTech (498) and CountBench (540). Each DocCount page is also dense: 2,555 target regions in total, 4–45 per page (median 5), all polygon-grounded.
W4: "agentic". In the camera-ready version, we will rename it "VLM-guided proposal grouping" and present it only as a diagnostic. The part we consider a contribution is the dataset-level finding it starts from: block-level text annotations show that current detectors over-fragment text blocks (3.3 predicted boxes per ground-truth block; 66% of blocks split).
W6: CJK. This question shows another use of the data. ADOPD's multilingual coverage and per-page metadata (language, complexity tier and text/visual profile; Appendix A.2) let us test the four explanations you list. We stratified the fine-tuned YOLOv12-X Doc2Box AP by language × the five complexity tiers × page profile, and compared each language with English at the same tier mix (Appendix A.16).
- Visual complexity: CJK pages are denser and more often in the hardest tier, but re-weighting English to a CJK tier mix moves its AP by at most 0.6. After matching, a gap remains: Japanese −5.9 AP, Chinese −2.9, Korean +2.0 on validation, and −4.0, −3.4 and +2.2 on test.
- Dataset imbalance: unlikely. Korean has the fewest pages (1,381 validation pages, against 3,283 for Chinese and 3,306 for Japanese) yet shows no gap.
- Where the gap is: visual-leaning pages (Japanese 62.3 vs English 70.4) and sparse pages (46.2 vs 64.6).
- Linguistic characteristics vs annotation conventions: the pattern is consistent with how CJK text is grouped into blocks on visually rich pages, that is, with text-block grouping conventions, rather than with page complexity. The data cannot fully separate linguistic properties from grouping conventions, and we state this as a limitation.
We hope these answers make clear that the paper's claims are about the utility of the data.
Methodological issues not resolved
Thanks for the response. The point about highlighting DoCoG and DocLayoutVL is not about the architectures. The works show that the proposed benchmark is not comprehensive and challenging enough - the bar for a benchmark is higher.
When pointed out that the usage of 'agentic' lacks justification, the authors simply plan to re-brand it as VLM-guided proposal grouping. This is not a good sign and shows lack of understanding about the topic.
Even if contribution is to D&B track, benchmarking can still throw light on unresolved problems and frontiers. But the current benchmark is ill-equipped to do so.
Given all these major issues, I retain my assessment.
Thank you for the careful review. We understand your overall assessment, and we still answer the main points, because several of them concern how the paper should be read. ADOPD 2026 is submitted under the datasets and benchmarks area. It does not propose a new model or method. Its claim is that the data is useful: it offers a combination of annotations that existing document datasets do not, and it exposes failure modes of current detectors and VLMs that existing benchmarks do not measure. We answer them in that light.
W1 / W7: contribution, concurrent work and venue.
W2: the counting experiments do not use the traces. We agree that the original Table 3 did not test this. We added a controlled ablation (General response §1, Appendix A.12): one backbone (Qwen3.6-35B-A3B), the same 442 questions and the same generation budget, varying only the region evidence given in the prompt.