- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper presents an approach to create connections between multimodal tool outputs (evidence atoms), generated model sentences and its contained claims. They use so called evidence ledgers to represent the interaction between evidence atoms, claims and sentences. Training on their algorithm uses the ledgers to improve the model's ability to support claims it makes based on grounded evidence from the tool output. They test their approach on 12 VQA benchmarks and 2 multimodal hallucination datasets.
Their main goal is to have fewer unsupported claims in the original model's output, and in addition more transparency by having trained submodules form a so-called "claim certificate", which allows interpreting the model's answers for evidence support. Multiple submodules are used during training and inference, such as a claim tagger, an evidence projector to move evidence into the same embedding space, a verifier head generating logits per claim and separate post-hoc (evaluation) scorer that generates claim support scores.
During training, the model answer is tagged by the claim tagger, the evidence is projected and both are inputted into the solver, which runs the algorithm to solve the ledger pairs into a claim budget plan. Those plans are then converted into losses for training, which forms part of a multi-objective loss function. They then update the adapters, projectors and tagger during training.
During inference, the pipeline also tags claims and projects evidence, and the solver generates the plans. The verifier head then outputs a score for each claim, and a separate post-hoc scorer generates the final support score, which together with some additional criteria are converted into verdicts of SUPPORTED, WEAK or NULL. Together, this forms the claim certificate.
Contributions are the training multi-objective loss function, the claim certificates, a new evaluation metric verified by a human study and replicating the approach on a second backbone.
Critical strengths
- The problem of hallucination of VLMs is well known and this approach connects generated claims, sentences and tool outputs in a transparent way, since per-claim evidence support enables verifying VLM output.
- The authors run a lot of ablations regarding verifying parts of the training objective, such as loss terms, the algorithm solving the transport problem, the null source for claims without a counter part, and verify the consistency of the ledgers.
- The human audit study is well designed and seems sound.
Critical weaknesses
- I often struggled to follow the paper. Tables, definitions of metrics and methods, and figures are not clearly labelled and seem in the wrong order also. In a lot of sections, the main results are in the appendix, and the main paper just references them. This made it very difficult to read in a flow (see questions 1, 2, 4, 6).
- It would be helpful to have a better defined task, and more examples, to explain how evidence ledgers and claim certificates look like in practice for different dataset task types (e.g. VQA tasks vs captioning vs hallucination benchmarks, see question 3 below)
- The figures are not readable with bad formatting, are way too small, which makes it hard to understand the task and the method.
Questions for authors
Questions:
- Table 1: Explanations for 6.2k, Cov., Lat. They are not defined in the main paper. I understand that only columns Hall.Acc and POPE F1 refer to those two HallusionBench and POPE. What are the datasets they are evaluating on for the other columns? The caption does not state this.
- "a text-only decomposer trained before this work" (L 337) and the "frozen evaluator J-ind" (L 339) are not defined in the main paper. But those are both critical components for the central metric for evaluation. Please define them and explain how they are trained.
- I can see how captioning tasks work well with this approach. However, how do we ensure that the model just doesn't generate any reasoning, and therefore doesn't hallucinate? Wouldn't this undermine the metric? This is mentioned in the appendix, but since the datasets and example ledgers are not explained well in the main paper, I find it hard to understand this.
- Tools are used to generate evidence atoms, but the specific tools are only defined in the appendix. What is input & output of the tool calls? This needs to be defined better and earlier in the paper. In addition, the method relies on tool confidence to define the atom capacity limit. However, I didn't find information on how they get the tool confidence.
- What is currently the input into the evidence projector? Are tools just used as text-only in the input? Would a multimodal representation of tool outputs (e.g. manipulated images with lines, bounding boxes, ...) work here and improve the evidence projection, and therefore the overall algorithm?
- For section 5.5, what are the 5 corruptions? Are they training models here on the corrupted data?
- How often do the tools miss correct evidence? If no evidence is found, the claim is penalised in training and marked NULL. How does the tool performance affect overall performance? This is touched on in the appendix, but the main paper would benefit from this.
Suggestions:
- Some re-ordering of sections, and clean up of the figures, captions and tables would make the paper more readable. In the current state, it seems like too many important details are hidden in the appendix.
- Section 5.2 describes the main results, and mentions mainly numbers from the appendix. I think it would be beneficial to have a bigger results table in the main paper. I think some of the ablations for the loss objective could be moved into the appendix to make more space (e.g. Table 3). Table 1 is unclear on what dataset it reports on.
- I would move effects of tool quality (Q7) and vague and empty answers (Q3) into the main paper.
- The figures need fixing, the table font needs to be larger. They are both difficult to read.
8 comments
Thanks again for your opinion, and in particular for whether the lower unsupported rate could have been bought by saying less; that question shaped the adequacy study. Our reply above gave the headline answers at the character limit, so we add the supporting measurements here, together with a short account of how the main text now reads on its own.
The purple text marks both revised text passages and original submission text for addressing reviewer questions, highlighted and reordered for readability. Pages are those of the revised PDF.
Q3, in full. Beyond the adequacy judgement (84.6 against 83.1% of prompts answered correctly and adequately, pp with interval ; 83.7% for on-policy grounder-DPO), three specificity measures on the 520-prompt audit show no drift towards vaguer claims: filled typed slots per claim 2.71 against 2.70, claims whose head noun is a hypernym of the noun the backbone used 4.1 against 3.9%, claims carrying a number, date, or count 28.1 against 27.5%; blinded quality ratings (1 to 5, two raters, 200 prompts) are 4.21 against 4.19 (Appendix B, p. 26).
Robustness of the headline number (Section 5.3). Counting every excluded item (3.1% of claims) against the ledger shrinks the ledger–backbone gap from to pp, interval ; fully manual atomization on 250 prompts gives 11.3 against 4.9%; the gap holds under every leave-one-benchmark-out split; the two automatic graders and the human panel rank the systems with Kendall and (Figure A.1), and the ledger's margin over on-policy grounder-DPO is 2.5 to 2.7 pp under all three.
HallusionBench supplies half of the Avg$_{14}$ gain through a reduced "yes" bias: the rate of answering "yes" on "no" items falls from 42.4% (backbone) to 19.0%, pair consistency rises from 51.0 to 63.7%, and a yes/no logit-bias correction of the backbone tuned on held-out data recovers only part of this (34.6%, 53.9%, Hall.Acc 67.0 against 74.6; Table K.30, p. 59). Saturated document and OCR tasks barely move, while reasoning, chart, and grounding tasks gain one to two points.
Q4 and Q7, the tools' footprint. The tools produce an atom for 92.4% of the evidence items annotators cited (91.3% of objects, 95.8% of text lines, 88.7% of chart elements, 97.0% of video frames). On the 124 audited claims whose evidence they missed, 33 of the 115 supported claims are NULL and 46 WEAK, so a miss mostly withholds a verdict rather than inventing one; the 3 false SUPPORTED rows among the 39 there are reported with their interval (Table I.28, p. 56).
Reading the main text alone. Tables 1, 3, and 4 now hold the full baseline set, the long-form and RePOPE results, and the blinded audit; Section 5.1 defines every grader and population and Table 1's caption names the population of each column; Appendix B's provenance paragraph (p. 25) explains why the human-graded Cert. (84.2) and the automatic seed-17 value (83.96, Table G.18) differ; Figure J.13 (p. 58) adds a long-form description and a video question to the examples of Figures 1 and 3; the main-text tables are set at 7 pt without scaling, and the figure labels (5.8 to 7.6 pt) pass a programmatic check for overlaps.
The certificate in human hands. Fourteen trained annotators (200 prompts, three per prompt, blinded) preferred the ledger certificate in 64.8, 70.2, and 68.5% of judgements for helpfulness, trust, and auditability, needed 19.7% less verification time, and found 81% of unsupported claims against 69%; seeded errors showed the limit, 22% of false-SUPPORTED rows caught, which is why the deployment policy adds a random 10% spot-check of SUPPORTED rows (recall 34% at 6% more time; Appendices M and N, pp. 64 to 65).
We hope these details show that the soundness questions were met with measurements rather than assurances, and we are happy to supply any further detail.
Dear authors, thank you for your detailed clarifications!
After checking out the paper again, I think the authors have definitely improved the paper. I appreciate the added task definition and the added figure with the examples (Figure 3). The main results section reads a lot better now, with fewer references to relevant numbers in the appendix. I also appreciate the addition of the answer quality and blind spot section in the results. I however still think that many sentences are way too long (semicolons all the way), and the paper would overall benefit from shorter sentences which would make it a lot more easily readable.
Some suggestions:
- Figure 2 definitely still has overlap of components and looks rather messy
- For the task definition in the introduction: “we ask for” reads a bit awkward, and the double mention of “answer” makes this a bit confusing. How can an answer be input and output? This is my understanding of the task/ approach: The task is Visual Question Answering, where given an image/ video/… input and corresponding question, a model produces an answer. The goal is to have fewer unsupported claims in the model's answer. The authors therefore introduce a framework that links the claims in the model’s own answer to evidence from external tools. During training, claims that no tool output supports are penalised, which lowers the rate of unsupported claims. During inference, the same framework produces a per-claim certificate, giving the supporting evidence and a verdict with a controlled false-SUPPORTED rate.
Dear Reviewer hvK4,
Thanks for your suggestions. Each item gives the question, where the main text answers it, and the answer.
Q3, does the model gain by saying less? Section 5.2 (p. 8) and Appendix B. On the 520 audit prompts, annotators blind to system identity and shown no certificate judged whether each frozen answer correctly and adequately addresses the question, refusals counting as failures. The ledger is judged adequate on 84.6% of prompts against 83.1% for the backbone and 83.7% for on-policy grounder-DPO, a paired difference of +1.5 pp, interval [−0.6, 3.6], so no decline was observed; this is not a non-inferiority test, and the paper no longer says "at least as often". It emits as many claims per answer as the backbone (2.91 against 2.88), more supported claims (2.78 against 2.56), refuses marginally more prompts (3.1 against 2.5%), and gains on every benchmark of Table 2. Appendix B states one cost: 0.9 to 2.4 pp fewer correct claims about small objects, out-of-prompt classes, and non-Latin text, where the tools see least.
Q7 and Q4, the tools and their misses. Section 3.1 names the tools (Grounding DINO prompted with the 80 COCO classes plus the question's noun phrases, PaddleOCR, DePlot, a 1-fps frame sampler), says what one atom is, and defines conf_i per tool; thresholds, versions, and the prompt are in Appendix C; every atom in Figures 1 and 3 carries its tool and raw output. Misses were measured under three conditions (Table I.28, p. 56): on the 124 audited claims whose evidence the tools missed, certified coverage is 31.5% against 71.5% elsewhere, and 3 of 39 SUPPORTED rows are false, a subgroup rate of 7.7% with interval [1.6, 20.9] that the marginal guarantee does not control; random removal of 10 / 20 / 30% of atoms lowers coverage to 63.1 / 57.4 / 50.9% at a false-SUPPORTED rate of 2.4 to 2.6%; oracle atoms give 74.6% and Cert.F₁ 91.0; the conclusion lists tool recall among three limits.
Q1, the Table 1 columns. The caption states the population of every column: UCR_ver and UCR_J-ind pool the parsed claims of the fourteen benchmark slices and are seed means; hUCR, aUCR, Cert.F₁, and claim coverage are human-graded on the 520-prompt audit of seed-17 outputs; Hall.Acc and POPE F₁ are the benchmarks' own metrics; controls that reuse the ledger's 6,200 annotated claims are marked, with the partition in Table C.4; latency moved to Appendix G; the backbone row's coverage of 84.2%, the grounder's own rule coverage, is noted as unrelated to the ledger's Cert.F₁ of 84.2. A Protocol paragraph in Section 5.1 gives numerator and denominator for every quantity, and a provenance paragraph in Appendix B (p. 25) names population, label source, seed, and aggregation for every headline cell, including why the human-graded Cert.F₁ (84.2) and the automatic seed-17 value in Table G.18 (83.96) differ.
Q2, the evaluation atomizer and J-ind. Section 5.1: a text-only Qwen2.5-7B decomposer trained before this work on 1,500 human-decomposed answers, disjoint from the ledger's atomizer in data, architecture, and initialisation, 93.6% recall and 94.2% precision on 1,200 held-out claims; J-ind is a claim-support classifier fine-tuned from Qwen2.5-VL-72B on 12,000 claims annotated by a separate team, never updated.
Q5, the projector input. Section 3.1 and Table G.13 (p. 48): the tool's text embedding with frozen vision features of the atom's region; text alone gives UCR 5.6% and Cert.F₁ 80.9, the default 4.9 and 84.2, a rendered overlay 4.8 and 84.4 at 1.26x latency. Q6, the corruptions. Section 5.5 lists the five, applied to every system's inputs at seven severities with no training on corrupted data; recipes in Appendix H.
Task, examples, figures, density. The introduction's second paragraph states the task and inputs; Figures 1 and 3 show certificates for a description, a chart, a scene-text, and a diagram question, and Appendix J adds a long description and a video question (p. 58). Figures 1 to 3 are redrawn at full column width in a formal typeface; a programmatic check on the vector output finds no label overlapping or touching another and every label inside its box or on an opaque chip; the main-text tables are set at 7 pt without scaling. Density was reduced by structure, not by removing results: the Findings open with the three main results and define certified coverage and the two loss terms where first used; Section 5.4 is three paragraphs (components; the strongest pipeline without transport; the certificate), each pointing to the appendix table with the detail; and, as you suggested, the main text keeps complete results tables (baselines in Table 1, long-form benchmarks and RePOPE in Table 3, the audit in Table 4), with the ablation detail in Appendix G.
We hope the adequacy and tool analyses answer the soundness questions and that the main text now reads on its own.