Papers › Dataset Cartography: Mapping and Diagnosing Datasets with Training Dynamics

Dataset Cartography: Mapping and Diagnosing Datasets with Training Dynamics

22 Sep 2020EMNLP 2020 11arXiv:2009.10795archive 2025-07-28

Swabha Swayamdipta, Roy Schwartz, Nicholas Lourie, Yizhong Wang, Hannaneh Hajishirzi, Noah A. Smith, Yejin Choi

Large datasets have become commonplace in NLP research. However, the increased emphasis on data quantity has made it challenging to assess the quality of data. We introduce Data Maps---a model-based tool to characterize and diagnose datasets. We leverage a largely ignored source of information: the behavior of the model on individual instances during training (training dynamics) for building data maps. This yields two intuitive measures for each example---the model's confidence in the true class, and the variability of this confidence across epochs---obtained in a single run of training. Experiments across four datasets show that these model-dependent measures reveal three distinct regions in the data map, each with pronounced characteristics. First, our data maps show the presence of "ambiguous" regions with respect to the model, which contribute the most towards out-of-distribution generalization. Second, the most populous regions in the data are "easy to learn" for the model, and play an important role in model optimization. Finally, data maps uncover a region with instances that the model finds "hard to learn"; these often correspond to labeling errors. Our results indicate that a shift in focus from quantity to quality of data could lead to robust models and improved out-of-distribution generalization.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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 16 code samples harvested from 5 repositories linked to this paper: 12 ran (of which 1 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 2 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 5 ran (5 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 8 samples from 4 repositories, 7 ran (3 with no instrument failure; 4 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 between 2026-09-22 and 2026-09-27 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

allenai/cartography officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 8 samples, 5 ran (0 instrument-failed) · 3 unverified report
DorBernsohn/TrainingDynamics mentioned on GitHubtfSyntology: not harvested report
dyahadila/ood_cartography mentioned on GitHubpytorchSyntology: 1 sample, 0 ran · 1 unverified report
szhang42/uneven_training_data mentioned on GitHubpytorchSyntology: 3 samples, 3 ran (2 instrument-failed) · 0 unverified report
beyondguo/TrainingDynamics pytorchSyntology: 3 samples, 3 ran (2 instrument-failed) · 0 unverified report
eliorc/tavolo tfSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 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

16 samples harvested: 12 ran (of which 1 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 2 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. 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.

2ran · violated contract
2ran · our draft was wrong
2ran; the contract check could not run
6ran
4unverified

Licence: 3 of the 16 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 5 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

allenai/cartography official repository 8 samples, 5 ran (0 instrument-failed) · 3 unverified
adapted_glue_compute_metrics cartography/classification/glue_utils.py ran Apache-2.0 (permissive) · c1dc8ee8436bbb66 · report fixture: returned dict · level recorded 2026-09-27
convert_string_to_unique_number cartography/data_utils_glue.py ran fingerprinted Apache-2.0 (permissive) · 18829c005e571204 · report fixture: signature string:str/0/str · returned int · level recorded 2026-09-25
convert_tsv_entries_to_dataframe cartography/data_utils.py ran Apache-2.0 (permissive) · d976a22c80de6352 · report fixture: signature tsv_dict:dict/0/?, header:str/0/str · returned DataFrame · level recorded 2026-09-25
label_balance cartography/classification/diagnostics_evaluation.py ran fingerprinted Apache-2.0 (permissive) · 17a0e1fc45469b30 · report fixture: signature label_list:list/1/int · returned float64 · level recorded 2026-09-25
read_jsonl in 136 papers cartography/data_utils.py ran Apache-2.0 (permissive) · d4036398be7d8fc9 · report fixture: signature file_path:str/0/str, key:str/0/str · returned dict · level recorded 2026-09-25
convert_mc_examples_to_features cartography/classification/multiple_choice_utils.py unverified Apache-2.0 (permissive) · 0356041f7d4f1629 · report
determine_categories_by_fields cartography/classification/diagnostics_evaluation.py unverified Apache-2.0 (permissive) · 8668f4254aab1786 · report
read_glue_tsv cartography/data_utils_glue.py unverified Apache-2.0 (permissive) · b03cdf908937ca31 · report
dyahadila/ood_cartography community (archive-listed) 1 sample, 0 ran · 1 unverified
compute_train_dy_metrics_per_epoch cartography/selection/train_dy_filtering.py unverified Apache-2.0 (permissive) · 13e0257678f83c36 · report
szhang42/uneven_training_data community (archive-listed) 3 samples, 3 ran (2 instrument-failed) · 0 unverified
compute_correctness cartography/selection/train_dy_filtering.py ran · violated contract fingerprinted Apache-2.0 (permissive) · b53e0e5cc0667b0b · report fixture: signature trend:list/1/float · returned float · level recorded 2026-09-22
compute_forgetfulness cartography/selection/train_dy_filtering.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed fingerprinted Apache-2.0 (permissive) · bd88c7f0a36c7e6a · report fixture: signature correctness_trend:list/1/float · returned int · level recorded 2026-09-22
compute_train_dy_metrics cartography/selection/train_dy_filtering.py ran · our draft was wrong Apache-2.0 (permissive) · 9aac3b7014417968 · report fixture: signature training_dynamics:dict/0/?, args:Args/0/? · returned tuple · level recorded 2026-09-22
beyondguo/TrainingDynamics community (archive-listed) 3 samples, 3 ran (2 instrument-failed) · 0 unverified
compute_correctness dy_filtering.py ran · violated contract fingerprinted no licence file found · pointer only · ebca92d1e4b67794 · report fixture: signature trend:list/1/float · returned float · level recorded 2026-09-22
compute_forgetfulness dy_filtering.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 270d424da751f2cf · report fixture: signature correctness_trend:list/1/float · returned int · level recorded 2026-09-22
compute_train_dy_metrics dy_filtering.py ran · our draft was wrong no licence file found · pointer only · fbb1ac1ee7b9badd · report fixture: signature training_dynamics:dict/0/?, include_ci:bool/0/bool, burn_out:int/0/int · returned tuple · level recorded 2026-09-22
eliorc/tavolo community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
DataMapCallback tavolo/learning.py ran MIT (permissive) · 63892da82b9ce195 · report fixture: returned DataMapCallback · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

4 assemblies on this paper: 4 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

4 sibling assemblies for Data Maps (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for Data Maps (graph method: Data Maps). 3 bricks; individually on a fixture: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. compute_train_dy_metrics entry · level 1 · ran · our draft was wrong · 9aac3b7014417968
  2. compute_correctness metric · level 1 · ran · violated contract · b53e0e5cc0667b0b
  3. compute_forgetfulness metric · level 1 · ran; the contract check could not run (RAISES) · bd88c7f0a36c7e6a

harvested Assembly for Data Maps (graph method: Data Maps). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 4 siblings

  1. DataMapCallback entry · level 1 · ran · 63892da82b9ce195

harvested Assembly for Data Maps (graph method: Data Maps). 2 bricks; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. compute_train_dy_metrics_per_epoch entry · level 0 · unverified · 13e0257678f83c36
  2. compute_correctness metric · level 1 · ran · violated contract · b53e0e5cc0667b0b

harvested Assembly for Data Maps (graph method: Data Maps). 3 bricks; individually on a fixture: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 4 siblings

  1. compute_train_dy_metrics entry · level 1 · ran · our draft was wrong · fbb1ac1ee7b9badd
  2. compute_correctness metric · level 1 · ran · violated contract · ebca92d1e4b67794
  3. compute_forgetfulness metric · level 1 · ran; the contract check could not run (RAISES) · 270d424da751f2cf

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2009.10795") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Model OptimizationOut-of-Distribution Generalization

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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