Papers › Soft-Label Dataset Distillation and Text Dataset Distillation

Soft-Label Dataset Distillation and Text Dataset Distillation

6 Oct 2019arXiv:1910.02551archive 2025-07-28

Ilia Sucholutsky, Matthias Schonlau

Dataset distillation is a method for reducing dataset sizes by learning a small number of synthetic samples containing all the information of a large dataset. This has several benefits like speeding up model training, reducing energy consumption, and reducing required storage space. Currently, each synthetic sample is assigned a single `hard' label, and also, dataset distillation can currently only be used with image data. We propose to simultaneously distill both images and their labels, thus assigning each synthetic sample a `soft' label (a distribution of labels). Our algorithm increases accuracy by 2-4% over the original algorithm for several image classification tasks. Using `soft' labels also enables distilled datasets to consist of fewer samples than there are classes as each sample can encode information for multiple classes. For example, training a LeNet model with 10 distilled images (one per class) results in over 96% accuracy on MNIST, and almost 92% accuracy when trained on just 5 distilled images. We also extend the dataset distillation algorithm to distill sequential datasets including texts. We demonstrate that text distillation outperforms other methods across multiple datasets. For example, models attain almost their original accuracy on the IMDB sentiment analysis task using just 20 distilled sentences. Our code can be found at https://github.com/ilia10000/dataset-distillation.

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 13 code samples harvested from 2 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 12 samples from 1 repository, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 1 sample from 1 repository, 1 ran (1 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

ilia10000/dataset-distillation officialmentioned in papermentioned on GitHubpytorchMITSyntology: 12 samples, 9 ran (0 instrument-failed) · 3 unverified report
Guang000/Awesome-Dataset-Distillation mentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Task-Specific Generative Dataset Distillation with Difficulty-Guided Sampling (arXiv:2507.03331; that paper's own run record: 1 ran (of which 0 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); nothing checks that they implement this paper's method. report
harshp1802/text-dataset-distillation mentioned on GitHubpytorchMITSyntology: 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

13 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 3 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.

10ran
3unverified

Licence: 0 of the 13 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 2 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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ilia10000/dataset-distillation official repository 12 samples, 9 ran (0 instrument-failed) · 3 unverified
clone_tuple networks/utils.py ran MIT (permissive) · 9ff25651ae35371b · report fixture: signature tensors:tuple/1/Tensor, requires_grad:NoneType/0/? · returned tuple · level recorded 2026-09-25
cross_entropy in 92 papers
census: 6 implementations from 8 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
basics.py ran fingerprinted MIT (permissive) · 971a7e33288dbfc5 · report fixture: signature pred:Tensor/2/float, soft_targets:Tensor/2/float · returned Tensor · level recorded 2026-09-25
encode in 73 papers utils/baselines.py ran MIT (permissive) · f5202ff9824f30c7 · report fixture: signature d:Tensor/1/int, state:State/0/? · returned Tensor · level recorded 2026-09-25
get_baseline_label_for_one_step utils/baselines.py ran MIT (permissive) · 8f695f4fc33f3364 · report fixture: signature state:State/0/? · returned Tensor · level recorded 2026-09-25
init_weights in 109 papers networks/utils.py ran MIT (permissive) · cabbd274bc3fcb07 · report fixture: signature net:callable/0/?, state:State/0/? · returned SimpleNet · level recorded 2026-09-25
read_bndbox datasets/pascal_voc.py ran MIT (permissive) · fdee81a9e734615a · report fixture: signature root:str/0/str, dataset:str/0/str, paths:list/1/str · returned list · level recorded 2026-09-25
to_np in 63 papers
census: 8 implementations from 14 papers, 2 distinct outputs across 2 buckets, one shared input per bucket
utils/io.py ran MIT (permissive) · 0250946399ff305f · report fixture: signature steps:list/1/tuple · returned list · level recorded 2026-09-25
to_torch in 53 papers
census: 5 implementations from 6 papers, 2 distinct outputs across 2 buckets, one shared input per bucket
utils/io.py ran MIT (permissive) · 63eebd9902e8150b · report fixture: signature np_steps:list/1/tuple, device:device/0/? · returned list · level recorded 2026-09-25
xentropy_cost basics.py ran fingerprinted MIT (permissive) · f26548178c3935fa · report fixture: signature x_target:Tensor/2/float, x_pred:Tensor/2/float · returned Tensor · level recorded 2026-09-25
load_results in 82 papers utils/io.py unverified MIT (permissive) · 062128c654a29276 · report
random_train utils/baselines.py unverified MIT (permissive) · c02233f6d63439a8 · report
read_split in 5 papers datasets/pascal_voc.py unverified MIT (permissive) · 4cd96988611c685e · report
harshp1802/text-dataset-distillation community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
init_weights in 109 papers networks/utils.py ran MIT (permissive) · e0e7604fc1f63651 · report fixture: signature net:callable/0/?, state:State/0/? · returned MinimalNet · level recorded 2026-09-24

Tasks

Data SummarizationDataset DistillationImage ClassificationSentiment Analysisimage-classification

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ConvolutionDense ConnectionsLeNet

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