Source-linked AI summary
PlaylistEval: Can Video-Language Judges Be Trusted at Day Scale and Beyond?
Shayekh Bin Islam, Hwanjun Song
TL;DR
Existing video-judge benchmarks rely on short clips, often permit transcript-only judgments, and require costly human annotation, leaving day-scale reliability untested. PLAYLISTEVAL automatically constructs visual-error preference pairs over 100-hour playlists. Judge accuracy degrades as playlists grow, and the best judge reaches 75.4% pairwise accuracy.
Problem
Existing video-judge benchmarks use clips of only a few minutes, can permit transcript-only scoring, and rely on costly human annotation, leaving reliability on day-long videos untested.
Source: §1 · p. 1Method
PLAYLISTEVAL automatically builds long-video preference pairs by grounding questions in distant playlist evidence and deriving distractors through controlled visual degradation.
Source: §1 · pp. 1–2, §3.2 · p. 5Results
Judge accuracy degrades as playlists grow, and the best judge reaches 75.4% pairwise accuracy.
Source: §1 · pp. 2–3Takeaways & Limitations
Ultra-long spatio-temporal verification remains largely unsolved, including for judge models fine-tuned on short clips.
Source: §5 · p. 10The benchmark uses public YouTube videos, whose URLs may become inaccessible if owners remove videos or make them private.
Source: ETHICS STATEMENT · p. 10
Abstract
from arXiv · showhide
Video-language models are increasingly used as judges of video understanding, both for evaluating model outputs and for training reward models. Whether their judgments remain reliable when the evidence is buried in day-long videos has yet to be established. Existing benchmarks cannot answer this. Their videos are typically only a few minutes long, many answer pairs can be separated from the transcript alone, and collecting human judgments does not scale to ultra-long videos. We introduce PlaylistEval, an agentic framework that builds video-language judge benchmarks over 100-hour playlist collection without human annotation. It automatically generates questions with paired answers whose differences are controlled by causal degradation, so that every pair demands retrieval across the collection. The resulting benchmark contains 630 pairs across seven domains spanning both static and dynamic knowledge, and on a stratified subset of 152 pairs it agrees with human judgments 93.0% of the time (IAA 0.781). Evaluating 17 omnimodal and multimodal models from eight families reveals that frontier judges reach only 75.4% pairwise accuracy, while open-source judge models perform far behind. We further show that both retrieval and final judgment depend on using multiple modalities, and that judge accuracy degrades as the playlist set grows. We release our pipeline, benchmark, and evaluation code at https://playlisteval.github.io.
1 INTRODUCTION
PLAYLISTEVAL targets the lack of scalable tests for video-language judges on day-scale collections by automatically building long, visually grounded preference pairs. Its evaluations show that judge accuracy remains limited and sensitive to playlist length, modality, and answer order.
1 INTRODUCTION
- Existing judge benchmarks use short videos, can allow transcript-only scoring, and require costly annotation for fine visual detail; long-video judges’ reliability beyond an hour remains unknown.The paper notes that short benchmark videos rarely require deciding where to look, while annotation costs constrain domain breadth and rebuilding.Source: §1 · p. 1
- PLAYLISTEVAL automatically builds 630 preference pairs across seven domains from playlists of about 100 hours, with human annotators confirming 93.0% of sampled preferences (IAA 0.781).Its phases generate questions grounded in distant playlist moments and distractors with visual errors, while validity gates feed rejection reasons back to the generator.Source: §1 · pp. 1–2
- The benchmark controls playlist size, modality, and pair difficulty, and evaluates 17 models from eight families alongside four retrievers.These controls test whether accuracy changes with collection length, which modalities contribute, and how retrieval affects judging.Source: §1 · p. 2
- 75.4% is the best judge’s accuracy, versus 93.0% for humans; small models are near chance, and judges fine-tuned on short video fall to or below chance.Source: §1 · p. 2
- Judge accuracy drops from 1 hour to 100 hours; retrieval recovers up to +10.5 points, but the best retriever finds the right segments only 37.9% of the time.Source: §1 · p. 3
- Using frames or transcript alone costs 2–7 points against using both, so neither modality alone suffices for judging.Source: §1 · p. 3
- When answers swap sides, weaker judges reverse verdicts on roughly half of pairs, while stronger judges remain largely consistent.Examples include Gemma-4-26B-A4B and Gemini-3.5-Flash-Lite among weaker judges, and Qwen-3.8-Max and Gemini-3.7-Flash among stronger judges.Source: §1 · p. 3
2 RELATED WORK
Prior work develops multimodal reward models and judge benchmarks for images, text, and video, but video evaluation has focused on short clips. PLAYLISTEVAL distinguishes itself as an automated native-video benchmark for longer scenarios.
2 RELATED WORK
- Image reward models include LLaVA-Critic, InternLM-XComposer-2.5-Reward, Skywork-VL Reward (Wang et al., 2025b), and MM-RLHF.Source: §2 · p. 3
- Video judges are less explored: VideoJudge and Wei et al. (2026) develop judges validated mostly on clips of a few minutes.Source: §2 · p. 3
- Existing video-judge benchmarks use few-minute clips and costly human annotation; PLAYLISTEVAL presents itself as the first fully automated native-video judge benchmark.Source: §2 · p. 3
3 PLAYLISTEVAL: PLAYLISTS TO JUDGE BENCHMARKS
PLAYLISTEVAL builds preference pairs from long playlists through two generation phases and a self-correcting feedback loop. Verification gates and a difficulty gate select the final pairs.
3 PLAYLISTEVAL: PLAYLISTS TO JUDGE BENCHMARKS
- PLAYLISTEVAL automatically builds video-grounded preference pairs from playlist collections through two generation phases wrapped in a self-correcting feedback loop.The process selects final pairs without human annotation.Source: §3 · p. 3
- Human curation selects seven domains, yielding 29 playlists and 457 videos at about 100 hours per domain; an index represents 30-second chunks using sampled frames and transcripts.Chunk and segment embeddings form a searchable playlist index.Source: §3 · pp. 3–4
3.1 PHASE I: GENERATING QA OVER SCATTERED EVIDENCE
- Phase I pairs related but distinct distant segments, asks a question requiring both, and checks structural validity, video necessity, and answer sufficiency with cross-family verifiers.Each claim in the gold answer cites its supporting span.Source: §3.1 · pp. 4–5
3.2 PHASE II: GENERATING DISTRACTORS BEYOND THE TRANSCRIPT
- Phase II creates four transcript-indistinguishable visual degradations ranked 4–1 beneath the gold, then tests textual undetectability and video recoverability.The controlled visual errors vary in severity and preserve the gold answer’s length, tone, and structure.Source: §3.2 · p. 5
3.3 SELF-CORRECTING LOOP AND PAIR SELECTION
- Rejections feed the next generation attempt, and a pair survives if either weaker judge fails, yielding 630 pairs across 327 questions, mostly rating gaps 1–2.The difficulty gate uses two open-weight judges deliberately weaker than the judges evaluated later.Source: §3.3 · p. 6
- 93.0% human agreement (IAA 0.781) on 152 stratified pairs; pipeline verification cost about 0.5 USD per pair versus 4.7 USD for humans.Building the benchmark cost 352 USD, or roughly 1 USD per accepted question.Source: §3.3 · p. 6
4 EVALUATION
The evaluation tests 17 video-language judges using retrieved or uniformly sampled evidence and measures pairwise accuracy across playlist lengths, input modalities, reasoning settings, and error types.
4 EVALUATION
- The evaluation covers 17 models from eight families, scores preference-pair accuracy, and compares retrieved frames with uniform sampling.Judges receive 128 frames; audio-capable models additionally receive chunk audio, while others receive ASR transcripts.Source: §4 · pp. 6–7
4.1 TRUST: JUDGES FALL FAR SHORT OF HUMANS
- 75.4% pairwise accuracy for Gemini-3.7-Flash with retrieved evidence trails the 93.0% human agreement; Table 1 reports accuracy by domain and overall.The best judge remains substantially below human annotators on this benchmark.Source: Table 1 · p. 7, §4.1 · p. 7
- Open-weight judges mostly approach chance, while short-video critics score 47.8–52.7% and retrieval leaves them unchanged or slightly worse.Only Gemma-4-26B-A4B rises clearly above the 50% chance floor among the open-weight general-purpose models.Source: §4.1 · pp. 7–8
4.2 LENGTH: ACCURACY FALLS AS THE PLAYLIST GROWS
- Accuracy declines as the haystack expands; retrieval narrows but does not close the length penalty, and its advantage reaches +10.5 points at the full domain.Under uniform sampling Gemma-4-26B-A4B loses 13.7 points from oracle to full scope, versus 3.2 points with retrieval.Source: Figure 4 · p. 8, §4.2 · p. 8
4.3 MODALITY: NEITHER FRAMES NOR TRANSCRIPT SUFFICES
- Combined frames and transcript perform best; removing either costs 2–7 points across judges because deciding visual evidence and surrounding narration both matter.Figure 5 compares judge accuracy under vision-text and vision-audio retrieval while varying the judge’s input stream.Source: §4.3 · p. 8, Figure 5 · p. 9
4.4 BOTTLENECK: FINDING THE EVIDENCE, NOT SEEING IT
- More reasoning or visual detail barely closes the gap, while faster audio modestly improves accuracy at lower cost, pointing to evidence search as the constraint.Reasoning lifts Gemini-3.5-Flash-Lite by 7.8 points over minimal, then only 0.5 points from low to high; doubling pixel-budget cost changes accuracy by at most 1.3 points, while 2× audio cuts cost 25% and improves accuracy 1.6 points.Source: §4.4 · p. 9
4.5 ERROR ANALYSIS
- Among 100 examined errors, retrieval dominates (~61%), followed by reasoning (~16%), frame sampling (~15%), perception (~6%), and annotation noise (~2%).The authors manually inspected errors made by the four strongest judges.Source: §4.5 · pp. 9–10
5 CONCLUSION
The paper concludes that PlaylistEval automates benchmark construction over 700 hours of playlist collections, while current judges remain unreliable at ultra-long spatio-temporal verification. Its materials are slated for release, and the benchmark’s video sources are public YouTube content that may later become inaccessible.
5 CONCLUSION
- PlaylistEval constructs video-language judge benchmarks over 700 hours of playlist collections without human annotation, and the analysis finds ultra-long spatio-temporal verification remains largely unsolved.The conclusion also reports a gap between human and model accuracy, weak transfer from short-clip fine-tuning, and declining accuracy as collections grow.Source: §5 · p. 10
- The authors provide retrieval, judge, and data-generation configurations, benchmark statistics, prompts, cost breakdowns, and the human-evaluation protocol, and plan to release the pipeline, benchmark, and code.Source: REPRODUCIBILITY STATEMENT · p. 10
- All benchmark videos are public YouTube content; URLs may become inaccessible, and corresponding files will be shared only with video-owner permission.Source: ETHICS STATEMENT · p. 10
A LIMITATIONS AND FUTURE WORK
The limitations are generator-family bias, evaluation cost that scales with pairs and judges, and predominantly English coverage. The retriever configuration uses chunk-level embeddings and returns top-ranked evidence chunks to judges.
A LIMITATIONS AND FUTURE WORK
- PLAYLISTEVAL relies on Gemini-3-Flash for generation while reserving other model families for verification, which may introduce systematic data bias.The authors suggest diversifying the generator pool as cheaper omni-modal models become available.Source: A LIMITATIONS AND FUTURE WORK · p. 16
- Scaling evaluation to substantially more pairs or judges increases cost, although automated evaluation remains an order of magnitude cheaper than human annotation at this video-duration scale.Source: A LIMITATIONS AND FUTURE WORK · p. 16
- Because the playlist collection is primarily English, the benchmark may not capture challenges specific to multilingual or low-resource settings.The authors note that ASR, embedding, and generative models may underperform at stages of the framework in those settings.Source: A LIMITATIONS AND FUTURE WORK · p. 17
B.1 RETRIEVER CONFIGURATIONS
- Each retriever indexes one vector per 30-second chunk; at evaluation, the top 64 chunks are passed to the judge in chronological order.The index contains about 100k float32 vectors across seven domains; retrieval settings and the transcript ASR system are listed in Tables 5 and 6.Source: Table 4 · p. 17, §B.1 · p. 17, Table 5 · p. 18
B.2 RETRIEVAL METRICS
Retrieval is scored over two evidence segments per question, using ranking metrics that reflect whether both segments are found and how highly they rank. The judge configurations standardize video evidence while varying the accompanying audio or transcript stream.
B.2 RETRIEVAL METRICS
- Each question’s domain corpus averages about 288 segments, with two gold segments per question and about 60 thirty-second chunks per segment.Chunks and query embeddings are unit-normalized, and segment rankings are based on chunk similarities.Source: §B.2 · p. 18
- Hitboth@k requires both evidence segments in the top k, while Hitany@k requires at least one; at N = 288 and k = 10, their random-selection chance floors are 0.11% and 6.8%, respectively.Source: §B.2 · p. 19
- nDCG@k is rank-sensitive and rewards placing both gold segments near the top because the judge’s frame budget is spread across retrieved chunks in rank order.Source: §B.2 · p. 19
B.3 VIDEO LM CONFIGURATIONS
- All 17 judges receive the same 128 frames at 640 × 480 plus audio for audio-capable judges or transcripts for the others.For Gemini audio judges, retrieved audio chunks are merged with pauses; Qwen3-Omni receives separate turns.Source: §B.3 · pp. 19–20, Table 7 · p. 19, Table 8 · p. 20
B.4 DATA GENERATION CONFIGURATIONS
The data-generation appendix identifies the models, input formats, and acceptance gates used by the pipeline.
B.4 DATA GENERATION CONFIGURATIONS
- Table 9 lists the pipeline models and their reasoning settings; no sampling parameters are overridden.Gemini models use default thinking, GPT models use high reasoning effort, and Qwen-3.7-Plus uses the provider default.Source: Table 9 · p. 20
- Each question is built from two clips, with each clip defined as a single segment of at most 30 minutes.Source: Table 10 · p. 21
- The pipeline gates run in listed order, so an item reaches costly video-processing steps only after passing cheaper checks.Blocks C1 and D2 are rule-based and call no AI model.Source: §B.4 · p. 20, Table 11 · p. 21
B.5 BENCHMARK STATISTICS
The appendix describes benchmark statistics, the knowledge types represented across its domains, and a complete example item. The example illustrates graded visual errors and cases where judges’ preferences diverge from annotators’ judgments.
B.5 BENCHMARK STATISTICS
- The benchmark-statistics table reports playlists processed, retained questions and pairs, and question and answer length distributions.Source: §B.5 · p. 21, Table 12 · p. 22
B.6 DOMAIN DESCRIPTIONS
- The seven domains cover static factual knowledge, evolving narrative or personal content, and mixtures of both.Examples include historical events and species biology for static knowledge, and TV plot lines and daily vlogs for dynamic knowledge.Source: §B.6 · p. 21, Table 13 · p. 22
B.7 A COMPLETE PLAYLISTBENCH ITEM
- In the worked item, graded wrong answers add or inherit visual errors, and one pair makes both difficulty-gate VLMs fail despite annotators preferring answer 3.A second pair shows a Rotterdam narration echoing another segment misleading GPT-5.6-Terra; the item marks supporting spans and altered claims.Source: §B.7 · p. 22
C ADDITIONAL RESULTS AND ANALYSIS
The additional analyses show that position bias tracks judge quality, agentic video search only modestly improves accuracy at oracle scope, and PLAYLISTEVAL accuracy tracks long-video QA ability. They also examine retrieval by segment and retriever and judge resource settings.
C.1 POSITION BIAS
- 14.8% and 21.6% letter agreement for Qwen-3.8-Max and Gemini-3.7-Flash contrast with 47.5% and 49.1% for Gemini-3.5-Flash-Lite and Gemma-4-26B-A4B.Lower letter agreement means strong judges switch letters when answer sides swap; weaker judges tend to retain the same slot.Source: §C.1 · p. 22, Table 14 · p. 24
C.2 EFFECT OF AGENTIC TOOL USE
- 65.9% accuracy with Gemini-3.5-Flash-Lite agentic tool use is 2.0 points above fixed-frame input and 27.1 points below human agreement at oracle scope.At this scope the judge receives only the two gold segments; the tool fetches its own evidence rather than receiving fixed sampled frames.Source: §C.2 · p. 24
C.3 CORRELATION WITH LONG-VIDEO UNDERSTANDING
- Pearson r = 0.96 (p = 6.3×10−4) links PLAYLISTEVAL accuracy with LVBench scores across seven judges, while the best judge reaches 75.4% versus 93.0% human agreement.The reported association suggests the automated pipeline recovers the model ranking of human-annotated benchmarks, while performance remains below human agreement.Source: §C.3 · p. 24, Figure 7 · p. 24
C.4 RETRIEVAL BY SEGMENT
- Both segments together are retrieved at roughly half the rate of either segment alone, although Hit@10 usually reports retrieval of at least one segment.The breakdown covers 343 questions.Source: §C.4 · p. 25, Table 15 · p. 25
C.5 FRAME BUDGET AND EMBEDDING WIDTH OF THE RETRIEVER
- 35.6 to 37.9 Hit@10 from 4 to 16 frames (peaking at 38.8 with 8 frames) accompanies 42.6 to 45.0 nDCG@10; reducing embedding width to 64 dimensions lowers Hit@10 to 23.3.Reducing WeMM-Embedding-9B from 4,096 to 1,024 dimensions costs 0.9 Hit@10 points at a quarter of the storage; at 64 dimensions the stored vector shrinks from 16 KB to 256 B.Source: §C.5 · p. 25, Figure 8 · p. 25
C.6 PIXEL BUDGET AND AUDIO SPEED OF THE JUDGE
- A larger pixel budget does not improve Gemma-4-26B-A4B accuracy when frames are pooled to the same number of visual tokens.The larger budget sharpens frames before pooling; the supplied results do not report an audio-speed outcome.Source: §C.6 · p. 26
D FAILURE CASES
The failure analysis traces errors through retrieval, frame sampling, perception, and reasoning, while the generation-cost analysis reports the benchmark’s total API spend and cost per accepted question.
D FAILURE CASES
- The failure-case panels mark the first lost-evidence step across retrieval, sampling, reading, and weighing, then show the evidence, answer differences, verdicts, and diagnosis.Retrieval and sampling are delivery steps; reading and weighing are the judge’s reasoning steps.Source: D FAILURE CASES · p. 26
- In the History example, three of four judges miss the higher-rated answer after the second segment is not retrieved and sampled frames miss the cheque’s leading 7.The question connects that 7 to seven Rome Statute no votes; only Qwen-3.8-Max chose the higher-rated answer.Source: Figure 9 · p. 27
- In the Documentary example, all four judges lose because none of 128 sampled frames shows the deciding on-screen species label, despite retrieving both segments.The transcript names a different species in an unrelated passage.Source: Figure 10 · p. 28
- Three of four judges misread a legible thermometer display in the Life example, while all four prefer the lower-rated answer in a separate reasoning-error example.The reasoning example’s served frame shows neither of the lower-rated answer’s two major fabrications, despite its greater rubric degradation.Source: Figure 11 · p. 29, Figure 12 · p. 30
E.1 DATA GENERATION COST
- $352.45 total API spend, or $0.94 per accepted question, includes retries and rejected candidates; native-video generation and checks account for almost all costs.Text-only verifiers account for under a tenth of the cost.Source: §E.1 · p. 31, Table 19 · p. 31, Table 20 · p. 31
E.2 DOWNSTREAM EVALUATION COST
One full benchmark-scoring pass across all seventeen judges cost $340.16, split between hosted-model charges and local GPU time.
E.2 DOWNSTREAM EVALUATION COST
- $340.16 covered one pass over all 630 pairs with 17 judges: $245.39 for hosted models and $94.77 for 23.7 NVIDIA H200 GPU-hours.Each judge scored every pair on retrieved evidence; ablations require additional passes.Source: §E.2 · p. 31, Table 21 · p. 32
F HUMAN EVALUATION DETAILS
Workers compared two answers against retrieved evidence and submitted a forced choice with an explanation. On 152 pairs, human ratings largely supported the benchmark’s intended preferences.
F HUMAN EVALUATION DETAILS
- Annotators received retrieved key moments for each question part and answer sentence, while underlined answer differences could be toggled to focus comparison.The moments were retrieved from both video segments using Qwen-3.7-Plus.Source: F HUMAN EVALUATION DETAILS · p. 32
- The annotation study collected 87 hours of work, with median task times of 7 to 11 minutes and average pay of $8.23 per hour.The reported average rate exceeded the US federal minimum wage.Source: F HUMAN EVALUATION DETAILS · p. 32
- Workers were screened by four Mechanical Turk qualifications, and 10% attention checks led to discarding ratings from workers who failed.Qualifications included a 95% lifetime HIT approval rate, at least 1,000 approved HITs, residence in a majority-English-speaking country, and Amazon Masters status.Source: F HUMAN EVALUATION DETAILS · p. 32
- 93.0% of individual ratings favored the benchmark’s intended answer, and majority judgments agreed on 147 of 152 pairs; annotator agreement was α = 0.781.The intended answer appeared in a random slot, and neither slot was favored.Source: F HUMAN EVALUATION DETAILS · p. 32, Table 22 · p. 35
- Figures 13–15 show the worker flow: instructions and payment, the question with evidence video and answers, then a forced choice and written explanation.Workers had to provide an explanation of at least 20 words before submitting.Source: F HUMAN EVALUATION DETAILS · p. 32, Figure 13 · p. 33, Figure 14 · p. 34
G PROMPTS
The prompts define how the pipeline generates and evaluates paired answers and multi-hop questions, emphasizing evidence grounding and screening for shortcuts such as transcript-only or memory-based answers. They also specify checks and retries for answer correctness and grounding, along with evidence selection for human evaluation.
G.1 REWARD MODEL EVALUATION PROMPT
- Judges must choose the better paired answer without ties, grounding judgments in retrieved frames and prioritizing accuracy when the evaluation criteria conflict.The meta-evaluation fixes Model A/B order per pair using a shared seed; replies without a parseable verdict or provider refusals receive chance credit.Source: §G.1 · pp. 36–37
G.2 DATA GENERATION PROMPTS
- The data-generation prompts specify each pipeline block’s model and response schema, with field descriptions carrying much of the question and answer specification.Slots are filled per request, and JSON schemas are passed to Gemini, GPT, and Qwen models.Source: §G.2 · p. 37, Table 23 · p. 38
G.2.1 TWO-SEGMENT QA GENERATION (B)
- Two-segment QA prompts require visually grounded, two-hop questions linking clips at least four minutes apart, with specific scene cues rather than direct entity attributes.The instructions target complex reasoning and require questions that cannot be answered from the transcript alone or general knowledge.Source: §G.2.1 · pp. 39–40
G.2.2 TRANSCRIPT-ONLY ANSWER (C2)
- Transcript-shortcut screening tests whether questions can be answered from transcripts alone by comparing a transcript-only answer with the gold answer.Each segment’s transcript is mixed with two further 30-minute windows from another playlist video, shuffled per item to make relevant evidence harder to locate.Source: §G.2.2 · p. 41
G.2.3 PARAMETRIC ANSWER (C2)
- Parametric-recall screening tests answers generated from the question alone, rejecting a question only when both generator-verifier combinations judge the memory-only answer correct.The two combinations swap the generator and verifier models, while both generators receive the same prompt.Source: §G.2.3 · p. 41
G.2.4 ANSWER VERIFICATION (C2)
- A shared verification prompt compares shortcut answers with the gold answer, and a single “Yes” rejects transcript-shortcut questions while both combinations must say “Yes” to reject parametric questions.The verifier assesses whether the predicted answer resolves the multi-hop logic without fatal contradictions.Source: §G.2.4 · p. 42
- Answer verification scans the prediction for the reference’s core facts, accepting extra verbosity but returning “No” if a necessary logical hop is missing or a contradiction negates the truth.Its structured output places an explanation before a Yes/No factual-consistency verdict.Source: §G.2.4 · p. 43
G.2.5 VIDEO GROUNDING (C3)
- Grounding checks use the full ∼30-minute source videos and transcripts for both hops, with video-ID references identifying support for each hop and claim.Qwen-3.7-Plus receives the videos and transcripts; the generator’s two-segment decomposition is a checklist to verify, not assume.Source: §G.2.5 · pp. 43–44
- Query grounding requires both foundational hops to be explicit in the videos or transcripts; commonsense may connect them, but missing hops or specialized outside knowledge yield “No.”The conclusion itself need not be explicitly stated if the two facts and their logical connection are safely supported.Source: §G.2.5 · pp. 43–44
- Answer grounding is “Yes” only when every substantive answer claim is directly supported by the videos or transcripts, not merely plausible or answerable in principle.Absent, contradicted, hallucinated, or outside-knowledge details yield “No.”Source: §G.2.5 · p. 44
G.2.6 GRADED WRONG ANSWERS (D1)
- Four long-form degraded answers rated 4 to 1 are generated from a fixed gold answer and the same clips, with degradation increasing while length and structural depth remain similar.The prompt requires realistic, hard-to-detect errors rather than truncation or obvious contradictions.Source: §G.2.6 · p. 45
- Degradations must be plausible, transcript-invisible visual errors, not changes to text-verifiable facts such as names, statistics, event order, or spoken claims.Targeted cues include appearance, spatial position, gestures, props, environment, graphics, and visible crowd details.Source: §G.2.6 · pp. 45–46
- The reward-model schema identifies five question-dependent attributes with importance scores summing to 1, then analyzes gold-answer quality and degraded, constant, or improved attribute elements.Attribute analyses explain causal impacts rather than non-causal heuristics.Source: §G.2.6 · pp. 46–48
- The four ratings specify increasing visual degradation: minor alteration at 4, moderate substitution at 3, major event or subject change at 2, and a fully fabricated visual sequence at 1.Each answer must remain cohesive and plausible, with positive phrasing and no timestamps or meta-commentary.Source: §G.2.6 · p. 47
- The wrong-answer prompt requires each degradation element to have a clear role in the enhancement and an explained direct causal impact on the improvement.These are the stated criteria for graded wrong answers.Source: §G.2.6 · p. 48
G.2.7 RANKING WITHOUT THE VIDEO (D3)
- Two judges rank the gold answer with four degraded answers using text only; a set is rejected only if both recover the intended order.Gemini-3.1-Pro and GPT-5.4 see shuffled, identically formatted candidates without the video or transcript, using question-specific attributes.Source: §G.2.7 · p. 48
G.2.8 RANKING WITH THE VIDEO (D4)
- Qwen-3.7-Plus ranks the four degraded answers against the two videos and transcripts, and a set passes only if the intended order is reproduced exactly.The gold answer is omitted, and each candidate includes its intended degradation analysis for internal verification.Source: §G.2.8 · p. 49
G.2.9 REGENERATION FEEDBACK (E)
- After a gate failure, its reason is added to the relevant generation prompt and the item is regenerated, up to the attempt limit.Feedback distinguishes question-and-answer retries from wrong-answer retries, where the question and gold answer remain fixed.Source: §G.2.9 · pp. 50–51
- Wrong-answer retries request four visual-only degradations that evade text-only detection but remain detectable with the video.Feedback requires nonempty degradation analyses for each rating from 4 to 1 and advises altering visual details readers cannot infer from the question or gold-answer wording.Source: §G.2.9 · p. 51
G.3 HUMAN EVALUATION EVIDENCE PROMPT
- For human evaluation, Qwen-3.7-Plus reads both full segments and transcripts to select 30-second evidence clips for question aspects and every reference-answer sentence.Videos are downscaled to 480p, stripped of audio, and encoded at 2 fps; timestamps use each segment’s own clock, and the pass reads the videos rather than reusing generator timestamps.Source: §G.3 · p. 51