- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
VidDeduce is a training-free agent for long-video question answering. It builds a caption database, then uses a planner to track evidence gaps and an observer to retrieve captions and inspect video intervals at coarse or fine scale. An NLI verifier distinguishes full support, partial support, contradiction and neutral observations to guide the next search. Using GPT-5.3 and Qwen2.5-VL-72B, it reports the highest scores in Table 2 on Video-MME, LongVideoBench and EgoSchema, with component ablations and search analyses.
Critical strengths
-
Distinguishing contradiction from missing or partial evidence is a sensible way to guide video search. The examples in Fig. 4 show why this matters: one requires abandoning a mistaken hypothesis, while the other requires examining the day sequence further. The planner–observer separation also makes the search decisions easier to follow.
-
The complete system performs well on three of four benchmarks (Table 2), and the evaluation includes component ablations and different reasoning and visual backbones. The discussion of the nine-point LVBench deficit to DVD is useful. In particular, Table 17 shows concrete details lost by the coarser captions rather than only reporting successful cases.
Critical weaknesses
- The experiments do not isolate the benefit of deductive verification.
The only direct comparison replaces NLI with an unspecified confidence mechanism on Video-MME (Table 3). The 69.89 to 71.33 improvement is 13 questions out of 900, with no reported uncertainty. Without the confidence prompt and stopping rule, it is difficult to know whether this tests four-way feedback or simply different prompting. No binary-verifier or no-verifier control is reported. The main baselines do not resolve this: DVD differs in caption granularity, visual model and search budget (App. A.3), while LensWalk shares the visual backbone but has no documented matched end-to-end rerun.
The verifier also receives retrieved captions as part of both the accumulated evidence and the new observation. Although the planner requests direct visual inspection, the verifier is not required to base its label on the visual findings (Eqs. 2–5; Tables 9 and 11). Caption-only and visual-only controls would be particularly informative here. The label definitions need a rule for observations that both support one gap and contradict another premise; excluding contradiction from Neutral does not address this overlap. Overall, the paper shows a competitive agent, but the contribution of the verifier remains uncertain.
- Several evaluation details affect the interpretation of the results.
The answer schemas allow only A–D (Tables 12 and 14), although EgoSchema has five options [Mangalam et al., 2023] and LongVideoBench permits 4–5 [Wu et al., 2024]. No remapping or separate schema is documented. Algorithm 1 also passes K and U to final deduction without incorporating the last non-global observation. The initial caption-only shortcut bypasses verification, but its decision rule and exit rate are not given. These details need to be resolved before the reported evaluations can be reproduced.
The grounding and efficiency claims need clearer accounting. Fig. 3(c)'s Combined Hit of 61.2% cannot be a pooled average of the 54.3% coarse and 38.8% fine observation rates; the unit over which intervals are combined is unspecified. The subsequent-entailment rates are also judged by the same verifier rather than independent evidence annotations (Sec. 4.2). For efficiency, the 162.1 active-search frames per Video-MME question exclude full-video captioning, which requires 1,200–2,400 frames per question at the benchmark's three questions per video (Sec. 4.1; Table 5). This supports a claim about active search, but not the cost of the full pipeline.
Questions for authors
- What exactly is the confidence baseline in Table 3, including its prompt and stopping rule? Are paired predictions or repeated-run results available for the 13-question gain?
- How were option E answers handled on EgoSchema? Does the selected LongVideoBench split contain five-choice questions, and if so, how were E answers handled? Were benchmark-specific schemas used?
- Does the implementation use the final observation differently from Algorithm 1? How often does the initial caption-only shortcut answer the question?
- Which Table 2 comparisons use matched models, captions and budgets? How does the verification mechanism differ from Logic-in-Frames?
- What is the sample unit and denominator for Combined Hit in Fig. 3(c), and what is the total cost per question after including caption generation?