- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper introduces Event-STVG, a task and benchmark for locating events and their participants in long videos. Given an event type, its order of occurrence, and a set of participant roles, models must locate the event in time and track each participant in space. The benchmark contains 4,016 annotated events from soccer and seven other domains, covering 26 event types and 30 roles. The paper evaluates nine general vision-language models and one specialized STVG model across different video lengths. It finds that models often confuse repeated events and struggle to locate the correct participants, with the best model achieving only 5.4% mean video IoU on 10-minute videos.
Critical strengths
-
Novel task design. Event-STVG extends traditional video grounding to event reasoning. It requires models to identify specific event occurrences and locate multiple participants in space and time.
-
Detailed benchmark and analysis. The benchmark covers eight domains with human-verified annotations. The experiments provide detailed analysis of model failures in event selection, spatial grounding, and participant localization.
Critical weaknesses
-
Imbalanced domain coverage. Soccer accounts for 3,516 of the 4,016 annotated events, while the other seven domains contain only 500 events.
-
Inconsistent evaluation settings. Different models use different video input settings. For example, GPT-5.6 Sol receives JPEG frames sampled at 2 FPS, while Qwen, GLM, and MiniMax receive native MP4 videos. Since video sampling settings can be controlled through model APIs, a more consistent evaluation would provide a fairer comparison.
-
Limited baseline comparison. The paper evaluates only one specialized STVG model, PTD. Its adapted input does not preserve the requested event order, which limits the comparison. Moreover, recent agent-based methods for video temporal grounding are not included.
Questions for authors
-
Could the authors provide results under consistent video input settings across models?
-
Could the authors include more specialized STVG models and recent agent-based VTG methods as baselines?
4 comments
Dear Reviewer Kc7V,
We have uploaded a revised version of the manuscript addressing the questions and concerns raised in your review. Thank you for your thoughtful feedback. We hope these revisions address your concerns and strengthen the evaluation of Event-STVG. We welcome any further comments or suggestions.
I appreciate the authors' rebuttal, which clarifies several points. Overall, I will keep my positive score of a weak accept.
Dear Reviewer Kc7V,
Thank you for following up after reading our rebuttal. We’re glad our responses helped clarify several points, and we appreciate your helpful feedback.
We thank the reviewer for recognizing the novelty of Event-STVG and the value of its annotations and analysis. We have revised the dataset and evaluation to address the concerns about domain coverage, input consistency, and baseline comparisons.
W1. Domain coverage
We have updated the non-soccer data and unified the context settings across all domains. The revised benchmark contains 4,036 events, 45 event types, and 27 semantic-role labels, comprising 7,342 event–role pairs. The full dataset remains soccer-heavy. However, our revised long-context evaluation and analysis now use 300 soccer events and all 520 non-soccer events, with the following composition:
Non-soccer events therefore constitute 63.41% of this cohort, increasing the domain diversity of the evidence supporting our long-context findings.
W2 and Q1. Consistent video inputs
We now provide explicit input configurations in Appendix B.2 and conduct paired input-alignment experiments for both short and long contexts.
For short contexts, we re-evaluate seven native-video models on the same 100 queries using 2-FPS, 512×288 frames under Oracle and one-minute settings (Appendix B.7). Entries below show native-video → aligned-frame m-vIoU (%). An asterisk indicates that the paired change’s source-clustered bootstrap 95% confidence interval excludes zero.
Input alignment improves Oracle grounding for four models and one-minute grounding for three; the remaining m-vIoU changes are inconclusive. Nevertheless, all six models excluded from the main long-context evaluation remain below 2% one-minute m-vIoU after alignment. For temporal localization, MiniMax improves by 22.19 pp; the other models’ m-tIoU changes are inconclusive.
For long contexts, we evaluate Qwen3.8-Max on a separate 100-query subset using Gemini’s exact frame protocol: 512×288 frames at 2 FPS for three and five minutes, and 900 uniformly sampled frames for ten minutes (Appendix B.8).
All long-context m-vIoU and m-tIoU differences have confidence intervals containing zero. Joint grounding remains limited under aligned inputs. Moreover, neither input format achieves complete grounding of all roles on the 40 multi-role queries in this subset at three, five, or ten minutes.
W3 and Q2. Additional specialized and agentic baselines
We add STVG-R1-7B, VideoMind-7B, and VideoTemp-o3, evaluating all three on the full 4,036 events under Oracle and one-minute settings. All receive complete event definitions, occurrence indices, and role specifications (Appendix B.12).
STVG-R1 selects role identities from tracked candidates. VideoMind retains its Planner/Grounder/Verifier, and VideoTemp retains its native agent loop. Both agentic methods use a shared YOLOv12x–SAM2.1–Qwen2-VL spatial backend to produce role trajectories.
The two agentic methods share the supplied interval and spatial backend under Oracle, explaining their identical Oracle scores.
To verify agent execution, we additionally test VideoTemp-o3’s tool workflow, since it did not invoke optional tools during Event-STVG evaluation. Under the same frozen deployment, we evaluate 30 Video-MME questions through each prompt path:
These checks confirm that autonomous tool invocation, cropping, and feedback processing are functional in the evaluated deployment.
We also directly test PTD’s interface limitation on 100 soccer queries (Appendix B.11). Providing full task instructions reduces one-minute m-vIoU from 2.10% to 1.22%, while valid native outputs fall from 180/183 to 51/183. We retain its native referring interface while acknowledging this limitation.