- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper focuses on “smoothing” failure of LLMs - where the models create confident syntheses of long documents but fail to faithfully reflect the underlying documents. The authors propose a claim-level scoring method, SMOOTH-SCORE, to measure this effect and find that models consistently produce stronger claims than they are supposed to.
Critical strengths
-
The research question is well motivated and could be helpful for critical fields that involve multiple document aggregation.
-
The evaluation experiments are conducted on a good number of datasets and systems, covering both open-source and proprietary models.
-
This paper is generally clearly written and easy to follow.
Critical weaknesses
-
Smoothing is an interesting failure but moderately narrow in scope for an ICLR paper. I think this paper could be much strengthened by additionally having either one of the following: 1. more in-depth analysis of why smoothing happens (i.e., a stronger Section 6); 2. solutions or even just practical takeaways that can help reduce smoothing failures.
-
Cross-system SmoothScores are not very comparable: Each claim is judged against the documents that the system cited, and different systems cite very different numbers of documents. Since smoothing scales with number of documents, the numbers are not comparable across systems, making the evaluation less useful for cross-system comparison.
-
Human annotators are used in the experiments (Table 3), but the details of human annotators (e.g., demographics, expertise) are not disclosed anywhere.
-
Some textual claims don’t match the tables or are inaccurate.
* “Gemini smooths severely on 26–43% of claims, roughly 2–3× the rate of the open-source agents” - but on DRB-II, QUEST gets a total of higher score of >=4 than Gemini, so the “2-3x” doesn’t hold. * “we find that roughly halves the smoothing σ = 1.65, σ ≥3 down 11 points.” - the drops (1.950>1.65 and 29.3->18.6) are much smaller than “halves” * Table 1 - is the 95% CI computed over each claim? So this would require the assumption that the claims are independent of each other, but claims can come from the same report and thus will be dependent on each other.
Questions for authors
See weakness.
3 comments
Part 2 of the response to Reviewer YkA7
Paper Errors
Thank you for pointing this out! We provide updates and details of the changes in the new draft for the updated claims:
Point 1: We agree the previous values were too broad and have removed this blanket comparison and now report Gemini’s severe-smoothing range directly: 26–43% across datasets (Section 4.1, line 266).
Point 2: We have removed the incorrect “roughly halves” wording and the revised Section 6 reports the expanded experiments and conclusions.
Point 3: For the 95% confidence intervals in Table 1 we use a cluster bootstrap over reports, not individual claims. For each system-dataset pair, we resample whole reports with replacement, keeping each report’s claims together, and recompute the mean SmoothScore over all claims in the sampled reports. This uses 10,000 resamples and we report the 2.5th and 97.5th percentiles. We have clarified this procedure in the revised paper.
Note on the revised PDF. In the paper, we have highlighted the portions with updates. Where an entire table, figure, or paragraph is new or rewritten, we have highlighted its caption or bold paragraph heading; where an entire appendix section is new, we have highlighted the section heading.
To keep changes easy to verify, we left the paper's structure unchanged and placed most new experiments in the appendix. For the final version, we will integrate the new experiments and results into the main text.
Official Comment by Authors
Thank you again for your thoughtful review. As the discussion period is nearing its end, we would like to kindly follow up on our rebuttal and ensure that we have adequately addressed your concerns. We would appreciate any further feedback and please let us know if there is anything we can clarify!
Part 1 of the response to Reviewer YkA7
Thank you for your comments!
We are posting a general update to the main paper based on added experiments requested by the reviewers. These updates add (1) an updated analysis of the relationship between cited documents and SmoothScore, (2) an extended validation of the SmoothScore pipeline using human annotations, additional judges and a common document pool experiment and (3) a more thorough and improved analysis of engagement of research systems with documents. Additionally, we also conducted a post hoc analysis of reports generated and added 2 extra systems (Sol and Opus). Any additional experiments or clarifications are present in the appendix.
As requested by the reviewers, we also report the answer coverage using the gold rubrics presented by the different benchmarks. However, we retain the claim that SmoothScore tests a failure distinct from coverage. This is added as an external evaluation of the quality of generation to ensure that any changes do not compromise performance of the generation in any other axes.
Addressing the weaknesses below:
Our interventions (in Section 6) are practical fixes to reduce smoothing. We find that providing the full documents in context or giving instructions to not smooth claims, reduces smoothing. For instance, with all documents in context, SmoothScore for Sonnet reduces from 2.48 to 2.38, and with instructions alone it reduces from 2.48 to 2.16. Combining the two gives the largest reduction (1.52 on Luna and 1.78 on Sonnet) showing that smoothing reflects both limited engagement with sources and how conclusions are presented.
Another way of reducing smoothing (post-hoc) is to revise an existing report against its cited documents with our intervention instruction (to not smooth claims). This allows the model to revise the original report, keeping the original content and making fixes where needed. Revision reduces smoothing and the share of materially smoothed claims, while rubric coverage is retained or improved.
The full table is provided in Section 6, Table 5. Our aim is to release our pipeline as a harness for any search-based agent to use (during generation or post-hoc). We leave training-based methods for improvement to future work.
We provide results for this in the comments for reviewer e41a. Our findings indicate a weak correlation between SmoothScore and the number of cited documents across systems (ρ = 0.35, p = .064), with a near-zero pooled within-system correlation (ρ = 0.04, p = .26; Appendix B, Table 11), and we have updated our observations accordingly (Section 4.1, line 296). We also ran an additional shared corpus experiment of 10 documents per question to isolate synthesis (Details in Appendix E). Comparing both conditions on the same questions, Luna has the lowest SmoothScore and Gemini the highest SmoothScore overall. Gemini’s mean score changes little (3.25 → 3.18), despite receiving roughly a quarter as many documents as it normally cites. Only QUEST is the outlier showing the largest overall reduction (2.77 → 2.28), reaching a SmoothScore comparable to Sonnet’s (2.29).
The two annotators of the pipeline are graduate researchers in Computer Science with experience in LLM evaluation and in reading literature in the evaluated domains. All annotations were provided independently using the same rubric as the judge without any access to system identity or judge scores.