Papers › MuMiN: A Large-Scale Multilingual Multimodal Fact-Checked Misinformation Social Network Dataset

MuMiN: A Large-Scale Multilingual Multimodal Fact-Checked Misinformation Social Network Dataset

23 Feb 2022arXiv:2202.11684archive 2025-07-28

Dan Saattrup Nielsen, Ryan McConville

Misinformation is becoming increasingly prevalent on social media and in news articles. It has become so widespread that we require algorithmic assistance utilising machine learning to detect such content. Training these machine learning models require datasets of sufficient scale, diversity and quality. However, datasets in the field of automatic misinformation detection are predominantly monolingual, include a limited amount of modalities and are not of sufficient scale and quality. Addressing this, we develop a data collection and linking system (MuMiN-trawl), to build a public misinformation graph dataset (MuMiN), containing rich social media data (tweets, replies, users, images, articles, hashtags) spanning 21 million tweets belonging to 26 thousand Twitter threads, each of which have been semantically linked to 13 thousand fact-checked claims across dozens of topics, events and domains, in 41 different languages, spanning more than a decade. The dataset is made available as a heterogeneous graph via a Python package (mumin). We provide baseline results for two node classification tasks related to the veracity of a claim involving social media, and demonstrate that these are challenging tasks, with the highest macro-average F1-score being 62.55% and 61.45% for the two tasks, respectively. The MuMiN ecosystem is available at https://mumin-dataset.github.io/, including the data, documentation, tutorials and leaderboards.

PaperPDFCodeCode 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 2 code samples harvested from 1 repository linked to this paper: 0 ran · 2 unverified.

By repository: official repository: 2 samples from 1 repository, 0 ran (0 with no instrument failure; 0 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.

MuMiN-dataset/mumin-build officialmentioned on GitHubpytorchMITSyntology: 2 samples, 0 ran · 2 unverified report
MuMiN-dataset/mumin-baseline mentioned on GitHubpytorchMITSyntology: not harvested report
MuMiN-dataset/mumin-trawl mentioned on GitHubpytorchSyntology: not harvested 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

2 samples harvested: 0 ran · 2 unverified. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2unverified

Licence: 0 of the 2 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 MuMiN-dataset/mumin-build. “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 “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.

MuMiN-dataset/mumin-build official repository 2 samples, 0 ran · 2 unverified
build_dgl_dataset src/mumin/dgl.py unverified MIT (permissive) · 23d05019b7c0921e · report
load_dgl_graph src/mumin/dgl.py unverified MIT (permissive) · fbde87e7db148788 · report

Tasks

ArticlesMisinformationNode Classification

Datasets

Introduced by this paper, per the archive.

MuMiNMuMiN-largeMuMiN-mediumMuMiN-small

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Node Classification MuMiN-large HeteroGraphSAGE Claim Classification Macro-F1 0.5980 #1 of 4 Archive leaderboard report
Node Classification MuMiN-large HeteroGraphSAGE Tweet Classification Macro-F1 0.6145 #1 of 4 Archive leaderboard report
Node Classification MuMiN-large LaBSE Claim Classification Macro-F1 0.5790 #2 of 4 Archive leaderboard report
Node Classification MuMiN-large LaBSE Tweet Classification Macro-F1 0.5280 #2 of 4 Archive leaderboard report
Node Classification MuMiN-large Majority class Claim Classification Macro-F1 0.4813 #3 of 4 Archive leaderboard report
Node Classification MuMiN-large Majority class Tweet Classification Macro-F1 0.4887 #3 of 4 Archive leaderboard report
Node Classification MuMiN-large Random Claim Classification Macro-F1 0.3879 #4 of 4 Archive leaderboard report
Node Classification MuMiN-large Random Tweet Classification Macro-F1 0.3690 #4 of 4 Archive leaderboard report
Node Classification MuMiN-medium HeteroGraphSAGE Claim Classification Macro-F1 0.5770 #1 of 4 Archive leaderboard report
Node Classification MuMiN-medium HeteroGraphSAGE Tweet Classification Macro-F1 0.5410 #1 of 4 Archive leaderboard report
Node Classification MuMiN-medium LaBSE Claim Classification Macro-F1 0.5585 #2 of 4 Archive leaderboard report
Node Classification MuMiN-medium LaBSE Tweet Classification Macro-F1 0.5745 #2 of 4 Archive leaderboard report
Node Classification MuMiN-medium Majority class Claim Classification Macro-F1 0.4806 #3 of 4 Archive leaderboard report
Node Classification MuMiN-medium Majority class Tweet Classification Macro-F1 0.4856 #3 of 4 Archive leaderboard report
Node Classification MuMiN-medium Random Claim Classification Macro-F1 0.3896 #4 of 4 Archive leaderboard report
Node Classification MuMiN-medium Random Tweet Classification Macro-F1 0.3772 #4 of 4 Archive leaderboard report
Node Classification MuMiN-small LaBSE Claim Classification Macro-F1 0.6255 #1 of 4 Archive leaderboard report
Node Classification MuMiN-small LaBSE Tweet Classification Macro-F1 0.5450 #1 of 4 Archive leaderboard report
Node Classification MuMiN-small HeteroGraphSAGE Claim Classification Macro-F1 0.5795 #2 of 4 Archive leaderboard report
Node Classification MuMiN-small HeteroGraphSAGE Tweet Classification Macro-F1 0.5605 #2 of 4 Archive leaderboard report
Node Classification MuMiN-small Majority class Claim Classification Macro-F1 0.4756 #3 of 4 Archive leaderboard report
Node Classification MuMiN-small Majority class Tweet Classification Macro-F1 0.4877 #3 of 4 Archive leaderboard report
Node Classification MuMiN-small Random Claim Classification Macro-F1 0.4007 #4 of 4 Archive leaderboard report
Node Classification MuMiN-small Random Tweet Classification Macro-F1 0.3718 #4 of 4 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