- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper examines how LLMs estimate the probability that a target exists after a partial search finds nothing. Some models report the unsearched fraction as this probability, whereas the correct answer requires applying Bayes’ rule with the prior probability that the target exists.
The experiments show this behavior does not stem simply from an inability to compute the posterior: providing the prior or changing the output format alters the models’ answers. When the prompt lacks sufficient information but still demands a probability, some models substitute a probability they can compute rather than stating that the requested one is undetermined.
Critical strengths
- The authors identify a useful distinction between reporting an inaccurate probability and reporting the probability of a different event, which matters when a system must make high-stakes decisions.
- The experiments are comprehensive, covering varied search coverage, priors, and output formats.
Critical weaknesses
- The motivation and presentation are difficult to follow and do not accurately reflect the work.
- The assumption that the percentage of the searched set is known is unrealistic.
- The paper is hard to read because notation and key terms are used before they are defined, which makes it difficult for first-time readers to follow.
- The original question does not specify a prior. A prior of 0.5 may serve as a useful reference, but the paper should state its prior assumption explicitly.
- The paper reports different behavior when coverage is given as a running percentage, which makes it unclear how broadly the findings generalize.
Questions for authors
- In real-world systems, how would the exact fraction of records already searched be known?
- If all records or logs are available, how does this setting differ from standard retrieval? Could the target not be located directly by indexing the records in a vector database and querying it?
- Since the prior is not given, how should an answer that relies on an explicitly stated prior be evaluated?
- Why does presenting coverage as a running percentage produce different behavior from presenting location shares?
5 comments
Thank you for the clarifications.
Addressed: W3 through the described notation revisions; W4/Q3 through prior-dependent scoring and acceptance of “undetermined” answers; and Q2 through the distinction between partial and exhaustive retrieval.
Remaining concerns:
W1: The connection between the controlled finding and the broader practical motivation remains insufficiently clear.
W2/Q1: The clinical example is helpful, but reliable coverage estimation for new searches and the effect of uncertainty in those estimates remain insufficiently addressed.
W5/Q4: I accept that the two coverage formats produce similar benchmark results. However, the unexplained differences across live-agent experiments leave the extent of generalization unclear.
I therefore maintain my rating of weak rejection, based on these remaining concerns.
We thank the reviewer for the follow-up and for listing their remaining concerns. Below we add new results and clarify the scope of our earlier findings.
W5/Q4: "... the unexplained differences across live-agent experiments leave the extent of generalization unclear." Our earlier reply left open why one live run shows almost no substitution, and we ran new live searches to address this. In the run the reviewer refers to, the coverage is given as a fraction of all documents. When we instead list the locations with their location shares and state the coverage as a fraction of those locations, 6 of 11 models give on the same search (App. B.5). This comparison changes two things at once, so it cannot tell us whether the added information or the wording is the cause. A further live search lists the locations without their location shares and gives only the cumulative coverage after each search. In this setting, 5 of the 13 scored models match in at least 90% of their 32 episodes (App. B.5). We therefore narrowed the claim to coverage stated as a share of the possible locations.
W2/Q1: "... reliable coverage estimation for new searches and the effect of uncertainty in those estimates remain insufficiently addressed." We agree that estimation matters, and we now test estimated inputs. In a split-sample analysis, we estimate coverage and base rate jointly on one half of the episodes and score decisions on the other half (App. H.2). Up to a base rate of 0.40, the posterior from the estimated inputs makes as many errors as with the true inputs. At a base rate of 0.60 on the emergency-department data, wrong decisions rise from 37 to ~44 per 100 failed searches, slightly worse than the model’s own number (~40). Even when we tell four models that the coverage is estimated and may be off by up to 0.10, they still report in almost every response (App. D.4). We agree that these results measure sensitivity to estimated inputs on our datasets, and do not validate an estimator for deployment or for new datasets, which we leave to future work (Sec. 5).
W1: "The connection between the controlled finding and the broader practical motivation remains insufficiently clear." We agree that the link should be more explicit. We ran the deployed classifier of Google’s Agent Development Kit on our inputs. 6 of the 8 scored models meet the substitution criterion, including one that computes the posterior on our benchmark (Table 8). This shows that the failure can pass through existing interfaces that require a probability, although we have not measured how often it occurs in practice.
We hope the answers above address the three remaining comments. If so, we again thank the reviewer for the detailed feedback and would ask them to kindly re-evaluate our work in light of the narrowed claim.
We thank the reviewer, whose summary states our claim accurately. Beyond Bayes' rule, the paper shows which wrong number appears and that calibration does not identify the event behind that number, and gives a check without labels that detects the substitution (general comment). A substituting model is defined in the general comment.
W2 and Q1. Is a known fraction searched realistic, and how would it be known? A pipeline has to measure the coverage. The paper supplies the coverage and does not test how a pipeline would estimate it, and Sec. 5 now says so. The coverage is the probability that the search finds a record that exists, which equals the share of records searched only when the target is equally likely to be any record and a search of a location finds every record in it. In the clinical records we measured it on the patients known to have the record, as the fraction for whom the searched tables contain it: 0.75 to 0.86 (App. B.2). The benchmark states δ because the test requires it. If the model estimated the coverage itself, the miss likelihood at its estimate and the posterior at some other coverage could give the same number (Sec. 2).
Q2. How does this differ from indexing everything? We agree that an exhaustive, exact lookup over a complete store resolves the question: a failed lookup then means the record is absent, and no probability is needed. The paper covers searches that stay partial or approximate. Search backends flag such searches in their responses. Elasticsearch by default returns partial results when shards fail or time out, GitHub's search API sets
incomplete_resultswhen a query times out, and Google Drive's setsincompleteSearchwhen not all documents were searched. These flags say a search was partial and do not give its coverage, which the pipeline must still measure. In our agentic run, models search an enterprise collection with tools under a budget, and 8 of the 21 substituting models (38%) report 1−δ when the section shares are stated (App. B.4). A prompt that states the coverage as a retrieval recall, drops the candidate list and states a base rate gets the posterior from 16 of 19 substituting models (App. D.4). The coverage also matters for decisions. At base rates where the coverage moves the posterior across the threshold, computing the posterior from each search's coverage makes up to 9.7 fewer wrong decisions per 100 failed searches on the enterprise data than the better of creating every record or no record (App. H.2).W5 and Q4. Why does a running percentage behave differently? On the benchmark a running percentage does not behave differently. Under the total after each scan, the 21 substituting models give 1−δ in 91% of 1,344 responses, 92% under the share table (Fig. 5(a), App. D.4). The run the reviewer cites differs in its search: its agents stopped at a median coverage of 13%, mostly because the budget ran out. Only 1 of its 176 responses (11 models, 16 episodes each) was at 1−δ. When a live search states the total after each scan (Table 6), GPT-5.5 gives 1−δ in all 128 episodes, Haiku 4.5 in most and Grok 4.20 Reasoning in 3 of 128 (App. B.5). The two runs also differ in budget and model set, so which of these differences removes the substitution is open.
W4 and Q3. The prior, and how a stated prior is scored. We score a stated prior against the posterior at that prior, within the same tolerance. Since the question does not state a base rate, 0.5 is only a reference prior, and an "undetermined" response or a stated dependence on the prior also counts as correct (Sec. 2). Given a required prior field, 6 of 11 models give the posterior at the prior they state (App. D.2). Urged to state a prior, two models that keep 1−δ, GPT-5.5 and GPT-5.4, give in 59 of 64 episodes a prior that contradicts their own number (App. D.7).
W1 and W3. Motivation, notation and terms. The introduction opens on one concrete scene, defines the coverage where it first appears, and Sec. 3.1 states the claim with its condition: given a coverage stated as location shares and no base rate, 58% of the 60 models fill the probability field with 1−δ (47% with the episodes that withhold the coverage pooled in). Sec. 2 defines rule and the kinds of prior in one place, and Fig. 1 shows example responses without rates.
If this answers how the coverage would be known (Q1) and why indexing leaves the question open (Q2), we hope the reviewer will reconsider the score. If a point still stands, please tell us which, and we will answer it.