Papers › Self-Chained Image-Language Model for Video Localization and Question Answering

Self-Chained Image-Language Model for Video Localization and Question Answering

11 May 2023NeurIPS 2023 11arXiv:2305.06988archive 2025-07-28

Shoubin Yu, Jaemin Cho, Prateek Yadav, Mohit Bansal

Recent studies have shown promising results on utilizing large pre-trained image-language models for video question answering. While these image-language models can efficiently bootstrap the representation learning of video-language models, they typically concatenate uniformly sampled video frames as visual inputs without explicit language-aware, temporal modeling. When only a portion of a video input is relevant to the language query, such uniform frame sampling can often lead to missing important visual cues. Although humans often find a video moment to focus on and rewind the moment to answer questions, training a query-aware video moment localizer often requires expensive annotations and high computational costs. To address this issue, we propose Self-Chained Video Localization-Answering (SeViLA), a novel framework that leverages a single image-language model (BLIP-2) to tackle both temporal keyframe localization and QA on videos. SeViLA framework consists of two modules: Localizer and Answerer, where both are parameter-efficiently fine-tuned from BLIP-2. We propose two ways of chaining these modules for cascaded inference and self-refinement. First, in the forward chain, the Localizer finds multiple language-aware keyframes in a video, which the Answerer uses to predict the answer. Second, in the reverse chain, the Answerer generates keyframe pseudo-labels to refine the Localizer, alleviating the need for expensive video moment localization annotations. Our SeViLA framework outperforms several strong baselines on 5 challenging video QA and event prediction benchmarks, and achieves the state-of-the-art in both fine-tuning (NExT-QA, STAR) and zero-shot (NExT-QA, STAR, How2QA, VLEP) settings. We also analyze the impact of Localizer, comparisons of Localizer with other temporal localization models, pre-training/self-refinement of Localizer, and varying the number of keyframes.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 7 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 6 ran (4 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yui010206/sevila officialmentioned in papermentioned on GitHubpytorchBSD-3-ClauseSyntology: 7 samples, 6 ran (2 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
3ran
1unverified

Licence: 7 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yui010206/sevila. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

yui010206/sevila official repository 7 samples, 6 ran (2 instrument-failed) · 1 unverified
generate_caption in 21 papers app/caption.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · 56f02812d66a0d11 · report fixture: signature model:callable/0/?, image:Tensor/4/float, use_nucleus_sampling:bool/0/bool, num_beams:int/0/int, max_length:int/0/int, min_length:int/0/int · returned list · level recorded 2026-09-24
get_concat_v in 11 papers app/dataset_browser.py ran · our draft was wrong BSD-3-Clause recorded; this copy not marked cleared · pointer only · 92f2e16ee0d3a24d · report fixture: signature im1:Image/0/?, im2:Image/0/? · returned Image · level recorded 2026-09-24
read_img in 41 papers app/calculate_coco_features.py ran · honoured contract BSD-3-Clause recorded; this copy not marked cleared · pointer only · 13a43a7d815937e6 · report fixture: signature filepath:str/0/str · returned Image · level recorded 2026-09-24
resize_img in 31 papers app/utils.py ran · our draft was wrong BSD-3-Clause recorded; this copy not marked cleared · pointer only · 926bb38f979a61ef · report fixture: signature raw_img:Image/0/? · returned Image · level recorded 2026-09-24
resize_img_w in 11 papers app/dataset_browser.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · f809f2ecf34c1c99 · report fixture: signature raw_img:Image/0/?, new_w:int/0/int · returned Image · level recorded 2026-09-24
sample_dataset in 20 papers app/dataset_browser.py ran BSD-3-Clause recorded; this copy not marked cleared · pointer only · 3d4bbb5ca53fd24a · report fixture: signature dataset:MockDataset/0/?, indices:list/1/int · returned list · level recorded 2026-09-24
compute_gradcam_batch in 11 papers app/multimodal_search.py unverified BSD-3-Clause recorded; this copy not marked cleared · pointer only · 3e12ea8c09674aa8 · report

Tasks

Language ModelingLanguage ModellingQuestion AnsweringRepresentation LearningTemporal LocalizationVideo Question AnsweringZero-Shot Video Question Answer

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Video Question Answering NExT-QA SeViLA Accuracy 73.8 #27 of 47 Archive leaderboard report
Video Question Answering NExT-QA (Efficient) SeViLA (4 frames) 1:1 Accuracy 73.8 #2 of 2 Archive leaderboard report
Video Question Answering STAR Benchmark SeViLA Average Accuracy 64.9 #3 of 17 Archive leaderboard report
Video Question Answering STAR Benchmark SeViLA (0-shot) Average Accuracy 44.6 #12 of 17 Archive leaderboard report
Zero-Shot Video Question Answer EgoSchema (fullset) SeViLA (4B) Accuracy 22.7 #28 of 29 Archive leaderboard report
Zero-Shot Video Question Answer EgoSchema (subset) SeViLA (4B) Accuracy 25.7 #13 of 14 Archive leaderboard report
Zero-Shot Video Question Answer IntentQA SeViLA (4B) Accuracy 60.9 #8 of 13 Archive leaderboard report
Zero-Shot Video Question Answer NExT-QA Sevila (4B) Accuracy 63.6 #19 of 27 Archive leaderboard report
Zero-Shot Video Question Answer TVQA SEVILA (no speech) Accuracy 38.2 #7 of 9 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections