Papers › MECD: Unlocking Multi-Event Causal Discovery in Video Reasoning

MECD: Unlocking Multi-Event Causal Discovery in Video Reasoning

26 Sep 2024arXiv:2409.17647archive 2025-07-28

Tieyuan Chen, Huabin Liu, Tianyao He, Yihang Chen, Chaofan Gan, Xiao Ma, Cheng Zhong, Yang Zhang, Yingxue Wang, Hui Lin, Weiyao Lin

Video causal reasoning aims to achieve a high-level understanding of video content from a causal perspective. However, current video reasoning tasks are limited in scope, primarily executed in a question-answering paradigm and focusing on short videos containing only a single event and simple causal relationships, lacking comprehensive and structured causality analysis for videos with multiple events. To fill this gap, we introduce a new task and dataset, Multi-Event Causal Discovery (MECD). It aims to uncover the causal relationships between events distributed chronologically across long videos. Given visual segments and textual descriptions of events, MECD requires identifying the causal associations between these events to derive a comprehensive, structured event-level video causal diagram explaining why and how the final result event occurred. To address MECD, we devise a novel framework inspired by the Granger Causality method, using an efficient mask-based event prediction model to perform an Event Granger Test, which estimates causality by comparing the predicted result event when premise events are masked versus unmasked. Furthermore, we integrate causal inference techniques such as front-door adjustment and counterfactual inference to address challenges in MECD like causality confounding and illusory causality. Experiments validate the effectiveness of our framework in providing causal relationships in multi-event videos, outperforming GPT-4o and VideoLLaVA by 5.7% and 4.1%, respectively.

PaperPDFCodeCode Syntology ran

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

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2409.17647")

Code

Syntology Ran 8 of 8 code samples harvested from 1 repository linked to this paper; 0 have no recorded run. Of those that ran: 5 ran · our draft was wrong; 3 ran with no contract checked.

By repository: official repository: 6 samples from 1 repository, 6 ran; 2 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

tychen-SJTU/MECD-Benchmark officialmentioned in papermentioned on GitHubpytorchMIT 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

8 samples harvested; 8 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

5ran · our draft was wrong
3ran

Licence: 2 of the 8 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 tychen-SJTU/MECD-Benchmark. Some samples are identical code Syntology first harvested from another repository; for those, this paper's copy is not located and its licence is not recorded. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

encode_image tychen-SJTU/MECD-Benchmark/mecd_llm_fewshot/gpt4o.py official repository ran MIT (permissive) · 6163d22216816e96 · report
encode_image_gpt4v tychen-SJTU/MECD-Benchmark/mecd_llm_fewshot/gpt4o.py official repository ran MIT (permissive) · 6553c070217c1ca9 · report
extract_first_bracket_content tychen-SJTU/MECD-Benchmark/mecd_llm_fewshot/gemini.py official repository ran fingerprinted MIT (permissive) · 061cb32540ba3358 · report
get_prompt tychen-sjtu/mecd-benchmark/mecd_vllm_fewshot/VideoChat2/multi_event.py official repository ran · our draft was wrong MIT (permissive) · 748d5a2586ca3178 · report
get_prompt2 tychen-sjtu/mecd-benchmark/mecd_vllm_fewshot/VideoChat2/multi_event.py official repository ran · our draft was wrong MIT (permissive) · db17c3cf4c7f44a9 · report
get_video_format tychen-sjtu/mecd-benchmark/mecd_vllm_fewshot/Video-LLaVA/videollava/eval/video/run_inference_causal_inference.py official repository ran · our draft was wrong fingerprinted MIT (permissive) · a9b8321d09aef11c · report
get_chunk identical code first harvested elsewhere ran · our draft was wrong fingerprinted licence of this copy not recorded · 42a46570620cd9fa · report
split_list identical code first harvested elsewhere ran · our draft was wrong fingerprinted licence of this copy not recorded · 076c252c52cbb161 · report

Tasks

Causal DiscoveryCausal Discovery in Video Reasoning

Datasets

Introduced by this paper, per the archive.

MECD

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Causal Discovery in Video Reasoning MECD VGCM Accuracy 71.20 #1 of 1 Archive leaderboard report
Causal Discovery in Video Reasoning MECD VGCM Ave SHD 4.19 #1 of 1 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.

Methods

Causal inference

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