raojay7/Awesome-LLMs-Data-AI

A curated and automatically updated collection of LLM data research, covering data substrates, data creation & selection, and data ingestion strategies across the full LLM lifecycle.

Python

109

268 commits

updated Sep 21, 2026

See the code

README

Awesome-LLMs-Data-AI

A Data-Centric Perspective on the Lifecycle of Large Language Models

A curated, operation-centered map of LLM data across the full lifecycle — from data substrates, to data creation and selection, to training- and inference-time information use.

Awesome Paper Survey References Literature Cut-off GitHub Stars Last Commit Literature Bot PRs Welcome

Paper · Taxonomy · Auto Tracking · Resource List · Cross-Tier Synthesis · Contribute


Why this repository?

LLM development is often organized by training stage (pretraining, SFT, RL) or by isolated techniques (synthetic data, selection, RAG, agents). This repository instead organizes the literature around the operation performed on information.

The accompanying survey asks three operational questions:

  1. What information-bearing artifacts or environments are available?
  2. How is supervision or data content created, transformed, filtered, or selected?
  3. How, when, and under what contextual conditions is available information consumed by the model?

This perspective makes it easier to place methods that cross conventional boundaries—for example, model-aware selection, data mixing, rejection-sampling loops, executable agent environments, retrieval, test-time search, and verification.

What you will find here

AreaCoverage
Data SubstratesPretraining corpora, instruction/preference data, reasoning and code resources, safety data, agent trajectories, benchmarks, executable environments
Data Creation & SelectionAnnotation, processing, prompting, distillation, synthetic data, back-translation, human–AI collaboration, symbolic generation, diversity/quality/model-aware selection
Data Ingestion StrategiesPacking, contextual conditioning, mixture weighting, curriculum, annealing, replay, multi-stage training, RAG, decoding, search, verification
Agentic DataTool-use data, multi-turn trajectories, environment synthesis, executable benchmarks, feedback-driven data loops
Cross-Tier SynthesisModel-conditional data utility, human specification/verification, executable data-producing systems, runtime information acquisition

If this repository is useful for your research, consider starring it. It helps other researchers discover the resource.


Taxonomy at a Glance

flowchart LR
    A["Tier 1 · Data Substrates<br/>What information exists?"]
    B["Tier 2 · Data Creation & Selection<br/>What supervision is created or changed?"]
    C["Tier 3 · Data Ingestion Strategies<br/>How and when is information consumed?"]
    M["Target Model<br/>Capability State"]

    A --> B
    A --> C
    B --> M
    C --> M
    M -. "errors · loss · confidence · interaction feedback" .-> B
    M -. "adaptive scheduling / retrieval" .-> C

Placement rule.
Tier 2 changes the supervision or data artifacts that exist; Tier 3 changes how available supervision or information is delivered to and consumed by the model.

The unit of analysis is the operation rather than the paper as a whole. A method can therefore span multiple tiers. For example, rejection-sampling fine-tuning may generate and filter trajectories in Tier 2, then immediately consume the retained trajectories during optimization in Tier 3.


How to Use This Repository

If you are interested in...Recommended entry point
Building or auditing a pretraining corpusData Substrates → Pretrain, Data Processing, Data Selection, Sample Mixing
Designing instruction-tuning / alignment dataSFT, Synthesis, Selection, Capability Alignment
Improving reasoning / code dataReasoning and Code, Symbolic Generation, Model-Aware Filtering
Building LLM agents / tool-use dataAgent and Tool Use, Agentic Data Pipelines
Studying curriculum, mixing, replay, or mid-trainingData Ingestion Strategies, Training Pipeline Optimization
Studying RAG / search / verification / test-time scalingTruthfulness & Consistency, Test-Time Strategy
Looking for the survey's main cross-paper insightsCross-Tier Synthesis

Automated Literature Tracking

To keep this repository useful beyond the survey's fixed literature cut-off, we provide an automated literature-tracking workflow built with GitHub Actions. The bot continuously discovers recent work related to the LLM data lifecycle, filters duplicates, assigns candidates to the operation-centered taxonomy, and proposes updates through pull requests for human review.

The automation is designed to assist curation rather than replace it: newly discovered papers are never auto-merged into the curated list.

How it works

Recent arXiv papers
        ↓
Topic-specific query families
        ↓
Date / category / LLM-data relevance filtering
        ↓
README + historical-database deduplication
        ↓
Operation-centered taxonomy classification
        ↓
Primary tier + optional cross-tier role
        ↓
Generated Markdown update
        ↓
GitHub Pull Request
        ↓
Human review → merge

The classifier follows the same placement principle as the survey:

  • Data Substrates — data-bearing artifacts, benchmarks, trajectories, and executable environments.
  • Data Creation and Selection — annotation, synthesis, transformation, filtering, and model-aware selection.
  • Data Ingestion Strategies — organization, mixing, curriculum, replay, retrieval, search, decoding, and verification.

Because the unit of analysis is the operation rather than the paper as a whole, the bot can also flag cross-tier papers. For example, a method may generate or filter supervision in Tier 2 and immediately consume that supervision during optimization in Tier 3.

Two update modes

ModePurposeOutput
Weekly literature updateDiscover newly released papers on a rolling windowUpdates the bot-maintained recent-paper block and opens a PR
Historical backfillScan an exact date range, e.g. 2026-07-01 → 2026-08-17Generates an independent Markdown report under updates/ and opens a PR

The historical mode is useful when the repository has not been updated for a period of time or when a new query family is introduced and earlier papers need to be recovered.

Repository automation

The implementation lives in:

.github/workflows/
├── update-papers.yml       # scheduled / manual weekly update
└── backfill-papers.yml     # exact-date historical scan

scripts/
└── paper_bot.py            # fetch → filter → deduplicate → classify → render

config/
└── paper_bot.yaml          # search queries, taxonomy keywords, thresholds

data/
└── papers.json             # persistent bot-curated paper history

The automatically maintained README block is bounded by:

<!-- AUTO-LITERATURE:START -->
## Recent Automatically Discovered Papers

> This section is generated by the weekly literature bot and reviewed through pull requests before merge.
> Last generated: **2026-08-24** · Showing up to **30** recent papers.

### Data Substrates

- **[Benchmarking Patent Drafting from Inventor-Style Disclosures](http://arxiv.org/abs/2608.21249v1)** — Lekang Jiang et al. (2026). *Other*
- **[Enhancing LLMs in Predictive Political QA with Semi-Structured Data](http://arxiv.org/abs/2608.21218v1)** — Yinan Liu et al. (2026). *Other*
- **[Designing a Robust LLM-Based Evaluation System for Agentic AI in Drug Discovery Through Human Alignment](http://arxiv.org/abs/2608.21057v1)** — Emma Granqvist et al. (2026). *Other*
- **[MigrationNarrate: A Dataset for Detection of Migration Narratives in YouTube Videos](http://arxiv.org/abs/2608.20984v1)** — Fatima Haouari et al. (2026). *Other*
- **[VortexChat: An agentic framework for autonomous multi-objective integrated photonic design](http://arxiv.org/abs/2608.20688v1)** — Faqian Chong et al. (2026). *Other*
- **[ARQ: Agentic CodeQL Query Refinement for C/C++ Vulnerability Detection](http://arxiv.org/abs/2608.20637v1)** — Chunyi Wang et al. (2026). *Other*
- **[Weighted Memory Tree: Remembering What Matters for Long-Horizon LLM Agents](http://arxiv.org/abs/2608.20631v1)** — Quang Dao et al. (2026). *Other*
- **[ConceptGuard: Benchmarking Context-Sensitive Unlearning in Large Language Models](http://arxiv.org/abs/2608.20338v1)** — Sahil Kale et al. (2026). *Other*
- **[From Agent Behaviour to Agent-Friendly Documentation: An Empirical Study of How Coding Agents Discover, Read, and Write Technical Documentation](http://arxiv.org/abs/2608.20195v1)** — Zhijun Gao et al. (2026). *Other*
- **[OenoBench: A Wine-Domain Benchmark for Knowledge-Grounded Evaluation of Large Language Models](http://arxiv.org/abs/2608.20106v1)** — Nikita Khudov (2026). *Other*

### Data Creation and Selection

- **[Target-Aware Calibration Data Selection for Preserving Uncertainty in Quantized Language Models](http://arxiv.org/abs/2608.21019v1)** — Zhen Yang et al. (2026). *Data Selection*
- **[An Agentic Approach for Active Data Collection, Travel Behavior Modeling, and Weather-Sensitive Demand Prediction](http://arxiv.org/abs/2608.20320v1)** — Narges Ahmadi et al. (2026). *Annotation / Processing*

### Data Ingestion Strategies

- **[Beyond Fault Localization: A Trajectory-Level Study of LLM Agents for Microservice Root Cause Analysis](http://arxiv.org/abs/2608.21310v1)** — Qisheng Lu et al. (2026). *Runtime Retrieval / Search / Verification*
- **[EnSI-RAG: Entity-Structure-Indexed Retrieval-Augmented Generation for Long-Document Question Answering](http://arxiv.org/abs/2608.21252v1)** — Xuanyu Meng et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Specification Portability Across LLM Development Agents: Cross-Agent Compatibility in Specification-Driven Software Migration](http://arxiv.org/abs/2608.21208v1)** — Oleg Grynets et al. (2026). *Runtime Retrieval / Search / Verification*
- **[ReFrame: Evidence-Guided Test-Time Safety Alignment in Multimodal Large Language Models](http://arxiv.org/abs/2608.21100v1)** — Wenzheng Jiang et al. (2026). *Runtime Retrieval / Search / Verification* · _Cross-tier: Data Substrates_
- **[Trustworthy RAG: An Evaluation Agent for Detecting Misinformation and Knowledge Poisoning in Generative AI Systems](http://arxiv.org/abs/2608.21095v1)** — Balkrishna Giri et al. (2026). *Runtime Retrieval / Search / Verification*
- **[$Z^2$-ACT: End-to-End Verifiable Agentic Intent Control for Open 6G RAN](http://arxiv.org/abs/2608.21049v1)** — Sunder Ali Khowaja et al. (2026). *Runtime Retrieval / Search / Verification*
- **[UpgradeBench: A Decision-Centric Benchmark for Upgrading Fine-Tuned LLM Specialists](http://arxiv.org/abs/2608.20918v1)** — Ye Chen et al. (2026). *Curriculum / Mid-Training / Replay*
- **[TRACE: Agentic Catalog Enrichment with Multi-source Evidence Grounding](http://arxiv.org/abs/2608.20844v1)** — Rohan Kumar et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Knowing but Not Saying: Preventing Factual Access Failures in LLM SFT via Recall-Anchored Distillation](http://arxiv.org/abs/2608.20794v1)** — Haodong Chen et al. (2026). *Curriculum / Mid-Training / Replay*
- **[Vis-Poison: Poisoning Visual Knowledge in Multimodal Retrieval-Augmented Generation](http://arxiv.org/abs/2608.20756v1)** — Rujin Liang et al. (2026). *Runtime Retrieval / Search / Verification*
- **[AsmEvo: Agentic Assembly-Level Optimization of AMD GPU Kernels with Functional Equivalence Verification](http://arxiv.org/abs/2608.20711v1)** — Ji Liu et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Towards Faithful Simulation of Human Shopping Behavior](http://arxiv.org/abs/2608.20707v1)** — Jiakai Tang et al. (2026). *Runtime Retrieval / Search / Verification*
- **[JuryProbe: An Empirical Consensus-Risk Diagnostic for Routing Reference-Free Factuality Judge Panels to Grounded Verification](http://arxiv.org/abs/2608.20607v1)** — Tianxin Zhou et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Terminal Agents: A Survey of AI Agents in Command-Line Environments](http://arxiv.org/abs/2608.20485v1)** — Yi Bin et al. (2026). *Runtime Retrieval / Search / Verification*
- **[MidTool: Mid-training Data Synthesis for Agentic Tool Use](http://arxiv.org/abs/2608.20314v1)** — Fengqing Jiang et al. (2026). *Curriculum / Mid-Training / Replay* · _Cross-tier: Data Creation and Selection_
- **[Inject, Align, Recover: Staged Post-Training for Retrieval-Free Document Knowledge Internalization](http://arxiv.org/abs/2608.20281v1)** — Qian Kou et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Decoding silent reading from non-invasive EEG](http://arxiv.org/abs/2608.20186v1)** — Ingo Marquardt et al. (2026). *Runtime Retrieval / Search / Verification*
- **[FormalTCS: Benchmarking End-to-End Frontier Formal Theoretical Computer Science Research of Large Language Models](http://arxiv.org/abs/2608.20153v1)** — Dingzirui Wang et al. (2026). *Runtime Retrieval / Search / Verification*

<!-- AUTO-LITERATURE:END -->

so the workflow never rewrites the manually curated core of this repository.

Curation policy

Automation is intentionally conservative:

  1. Discovery is automatic; acceptance is human-reviewed.
  2. Existing README entries and previously accepted bot records are deduplicated before proposal.
  3. The workflow prefers high-recall discovery followed by stricter relevance and taxonomy filtering.
  4. Ambiguous methods may receive a primary tier plus a cross-tier label.
  5. Important accepted papers can later be moved from the automatically maintained recent-paper block into the main curated sections.

This makes the repository a living companion to the survey while preserving the quality and interpretability of the manually curated taxonomy.


Scope and Update Policy

  • Survey literature cut-off: June 2026.
  • Repository status: living resource; a GitHub Actions literature bot tracks new candidate papers beyond the paper cut-off, with all additions reviewed through pull requests.
  • In scope: work where data resources, data construction/selection, information scheduling, retrieval, verification, trajectories, or executable environments play a substantive role in LLM development or evaluation.
  • Out of scope by default: architecture-only or optimization-only papers where the data lifecycle is incidental.
  • Source preference: primary papers, official project pages, ACL Anthology, OpenReview, arXiv, or official dataset/model repositories whenever available.

2026 coverage highlights

Recent additions reflected in the survey/repository include:

  • Research-level reasoning data: ResearchMath-14K.
  • Real and executable coding-agent data: Multi-SWE-bench, SWE-Chat, SWE-RL, SWE-Playground.
  • Tool-agent trajectories and environments: TOUCAN, FunReason-MT, UniToolCall, WebWorld, ClawGym.
  • Environment/data co-evolution: Agent-World, Nex-N1, ClawEnvKit, AgentFrontier.
  • Recent survey context: Agentic Tool Use in LLMs, Agentic Environment Engineering, and The LLM Data Auditor.

Contents

1. Surveys

Data Selection

Generation

Blogs

2. Taxonomy

We organize the LLM data lifecycle through an operation-centered, three-tier taxonomy. The goal is not merely to separate training stages, but to distinguish what information-bearing objects exist, how their content or membership is changed, and how available information is presented to and consumed by the model.

TierOperational questionScopeRepresentative examples
Tier 1: Data SubstratesWhat information-bearing artifacts or environments are available?Corpora, instruction/preference data, benchmarks, reasoning/code resources, trajectories, executable environmentsPretraining corpora, SFT/RL data, math/code benchmarks, tool-use trajectories, agent environments
Tier 2: Data Creation and SelectionWhat supervision exists, and how is it created or modified?Annotation, synthesis, transformation, filtering, diversity/quality/model-aware selectionDistillation, self-instruct, back-translation, symbolic generation, data filtering, influential-data selection
Tier 3: Data Ingestion StrategiesHow, when, how often, and under what context is information consumed?Packing, contextual conditioning, mixture weighting, curriculum, annealing, replay, retrieval, search, decoding, verificationSample construction, data mixing, mid-training, multi-stage curricula, RAG, test-time search

Placement rule. Tier 2 changes the supervision or data artifacts that exist; Tier 3 changes how available supervision or information is delivered to and consumed by the model. For example, offline data selection is primarily Tier 2, whereas dynamic data mixing is Tier 3. An agent trajectory is a Tier-1 substrate; generating or filtering trajectories is Tier 2; using them in iterative optimization or test-time interaction is Tier 3.

Cross-tier methods. The unit of analysis is the operation rather than the paper as a whole. Methods such as rejection-sampling fine-tuning or error-driven preference optimization can span multiple tiers: they may generate/filter supervision in Tier 2 and immediately consume the retained supervision during optimization in Tier 3.

3. Data Substrates

3.1 General Domain

3.1.1 Pretrain

3.1.2 SFT

3.1.3 RL

3.2 Specific Domain

3.2.1 Reasoning and Code

3.2.2 Safety and Alignment

3.2.3 Agent and Tool Use

3.3 Summary: Substrate Dynamics and Trade-offs

The substrate view highlights a shift from raw scale toward curated information density, and—especially for agents—from stored text/trajectories toward executable environments that can generate tasks, observations, failures, recovery paths, and verification signals on demand.

4. Data Creation and Selection

4.1 Annotation

4.1.1 Data Processing

4.1.2 Prompt Engineering

4.2 Synthesis

4.2.1 Sampling-Based

4.2.2 Data Transformation

4.2.3 Back-Translation

4.2.4 Human-AI Collaboration

4.2.5 Symbolic Generation

4.3 Selection

4.3.1 Diversity

4.3.2 Quality

4.3.3 Composite Strategy

4.4 Summary: Creation and Selection Trade-offs

Across creation and selection methods, the survey highlights three recurring transitions: teacher distillation → autonomous/self-play generation, static quality filtering → model-conditional utility, and stored examples → verifier-grounded or environment-generated supervision. Selection and synthesis increasingly interact through closed loops rather than remaining independent preprocessing stages.

5. Data Ingestion Strategies

5.1 Efficiency & Effectiveness

5.1.1 Sample Construction

Cross-tier note: this section focuses on the ingestion/optimization-time role of sample construction. Methods that generate persistent new supervision (e.g., rejection sampling or targeted error injection) also have a Tier-2 creation component.

5.1.2 Sample Mixing

5.2 Training Pipeline Optimization

5.2.1 Mid Training

5.2.2 Multi-Stage Training

5.3 Capability Alignment Strategies

5.3.1 Constraint

5.3.2 Cognitive Alignment

5.4 Truthfulness & Consistency

5.4.1 Consistency

5.4.2 RAG

5.4.3 Decoding

5.5 Summary

Data ingestion spans both training-time scheduling and runtime information use. Training-time methods determine how supervision is organized, weighted, ordered, replayed, or conditionally presented; runtime methods determine when self-generated or external evidence is retrieved, searched, decoded, or verified.

6. Cross-Tier Synthesis

The lifecycle view exposes several recurring transitions that are less visible when datasets, synthesis, selection, training schedules, and agent systems are studied separately:

  1. Static data quality → model-conditional utility. Data usefulness increasingly depends on the target model's current loss, confidence, errors, capability state, and learnability frontier.
  2. Instance-level annotation → system-level specification and verification. As synthesis becomes more autonomous, human effort shifts toward task specification, verifier design, environment construction, governance, and exception handling.
  3. Stored artifacts → executable data-producing environments. Agentic data increasingly includes environments that generate tasks, actions, observations, failures, recovery trajectories, and reward signals on demand.
  4. Offline data preparation → adaptive runtime information acquisition. Retrieval, search, verification, and test-time compute extend data optimization beyond parameter training.

These trends motivate treating data engineering as the joint design of artifacts, transformations, and adaptive information-use policies.

7.1 Data Resources and Governance

7.1.1 Domain-Specific Data Scarcity

7.1.2 Cross-Domain Data Reutilization

7.1.3 Data Sensitivity and Privacy

7.2 Data Creation and Selection

7.2.1 Agentic Data Pipelines and Closed-Loop Flywheels

7.2.2 Multi-source Synthesis

7.2.3 User Collaboration

7.2.4 Cross-modal Knowledge Utilization

7.2.5 Data Efficiency

7.2.6 Length-Aware Data Synthesis and Selection

7.2.7 Model-Aware Filtering

7.3 Data Ingestion Strategies

7.3.1 Unified Post-Training

7.3.2 Cross-Stage Data Reutilization

7.3.3 Data Unlearning

7.3.4 Test-Time Strategy

Citation

If you use this repository or the taxonomy in your research, please cite the accompanying survey:

@article{rao2025datacentric,
  title   = {A Data-Centric Perspective on the Lifecycle of Large Language Models},
  author  = {Rao, Jun and Liu, Xuebo and Yan, Haotian and Shen, Junjie and Mo, Haosi and
             Dong, Yanghaopeng and Yan, Zihao and Wang, Ziyi and Lin, Zepeng and Meng, Xiaojun and
             Yu, Zixiong and Deng, Liqun and Wei, Jiansheng and Wang, Yunhe and Zhang, Min},
  journal = {TechRxiv},
  year    = {2025},
  doi     = {10.36227/techrxiv.176620610.03288677/v1},
  url     = {https://doi.org/10.36227/techrxiv.176620610.03288677/v1}
}

For GitHub-native citation support, we also recommend adding a CITATION.cff file to the repository root.

Contributing

Contributions are welcome. Please open an issue or pull request to add a paper, dataset, benchmark, correction, or missing link.

To keep the list consistent:

  1. Use primary sources whenever possible — official paper, ACL Anthology, OpenReview, arXiv, or official project page.
  2. Place resources by operation, not only by training stage or application domain.
  3. Use cross-tier notes when needed. A method may appear under the tier corresponding to the operation being discussed while retaining a secondary role elsewhere.
  4. Avoid duplicates. Prefer the formally published version over an arXiv duplicate when both are available.
  5. Keep entries concise: Title — venue/year — link.
  6. For new 2026+ work, briefly explain why it changes or extends the taxonomy when the placement is non-obvious.

Suggested pull-request title:

[Add] <Paper / Dataset / Benchmark Name> → <Section>

Acknowledgements

We thank the authors of the papers, datasets, benchmarks, and open-source resources collected here, as well as community contributors who help keep the list accurate and up to date.


Data is not only what a model trains on — it is also what gets created, selected, scheduled, retrieved, verified, and regenerated throughout the model lifecycle.

Contributors

raojay7

155 commits

hiterlink

55 commits

chris13798

16 commits

luakcoder

15 commits

raojay7/Awesome-LLMs-Data-AI

A curated and automatically updated collection of LLM data research, covering data substrates, data creation & selection, and data ingestion strategies across the full LLM lifecycle.

Python

109

268 commits

updated Sep 21, 2026

See the code

README

Awesome-LLMs-Data-AI

A Data-Centric Perspective on the Lifecycle of Large Language Models

A curated, operation-centered map of LLM data across the full lifecycle — from data substrates, to data creation and selection, to training- and inference-time information use.

Awesome Paper Survey References Literature Cut-off GitHub Stars Last Commit Literature Bot PRs Welcome

Paper · Taxonomy · Auto Tracking · Resource List · Cross-Tier Synthesis · Contribute


Why this repository?

LLM development is often organized by training stage (pretraining, SFT, RL) or by isolated techniques (synthetic data, selection, RAG, agents). This repository instead organizes the literature around the operation performed on information.

The accompanying survey asks three operational questions:

  1. What information-bearing artifacts or environments are available?
  2. How is supervision or data content created, transformed, filtered, or selected?
  3. How, when, and under what contextual conditions is available information consumed by the model?

This perspective makes it easier to place methods that cross conventional boundaries—for example, model-aware selection, data mixing, rejection-sampling loops, executable agent environments, retrieval, test-time search, and verification.

What you will find here

AreaCoverage
Data SubstratesPretraining corpora, instruction/preference data, reasoning and code resources, safety data, agent trajectories, benchmarks, executable environments
Data Creation & SelectionAnnotation, processing, prompting, distillation, synthetic data, back-translation, human–AI collaboration, symbolic generation, diversity/quality/model-aware selection
Data Ingestion StrategiesPacking, contextual conditioning, mixture weighting, curriculum, annealing, replay, multi-stage training, RAG, decoding, search, verification
Agentic DataTool-use data, multi-turn trajectories, environment synthesis, executable benchmarks, feedback-driven data loops
Cross-Tier SynthesisModel-conditional data utility, human specification/verification, executable data-producing systems, runtime information acquisition

If this repository is useful for your research, consider starring it. It helps other researchers discover the resource.


Taxonomy at a Glance

flowchart LR
    A["Tier 1 · Data Substrates<br/>What information exists?"]
    B["Tier 2 · Data Creation & Selection<br/>What supervision is created or changed?"]
    C["Tier 3 · Data Ingestion Strategies<br/>How and when is information consumed?"]
    M["Target Model<br/>Capability State"]

    A --> B
    A --> C
    B --> M
    C --> M
    M -. "errors · loss · confidence · interaction feedback" .-> B
    M -. "adaptive scheduling / retrieval" .-> C

Placement rule.
Tier 2 changes the supervision or data artifacts that exist; Tier 3 changes how available supervision or information is delivered to and consumed by the model.

The unit of analysis is the operation rather than the paper as a whole. A method can therefore span multiple tiers. For example, rejection-sampling fine-tuning may generate and filter trajectories in Tier 2, then immediately consume the retained trajectories during optimization in Tier 3.


How to Use This Repository

If you are interested in...Recommended entry point
Building or auditing a pretraining corpusData Substrates → Pretrain, Data Processing, Data Selection, Sample Mixing
Designing instruction-tuning / alignment dataSFT, Synthesis, Selection, Capability Alignment
Improving reasoning / code dataReasoning and Code, Symbolic Generation, Model-Aware Filtering
Building LLM agents / tool-use dataAgent and Tool Use, Agentic Data Pipelines
Studying curriculum, mixing, replay, or mid-trainingData Ingestion Strategies, Training Pipeline Optimization
Studying RAG / search / verification / test-time scalingTruthfulness & Consistency, Test-Time Strategy
Looking for the survey's main cross-paper insightsCross-Tier Synthesis

Automated Literature Tracking

To keep this repository useful beyond the survey's fixed literature cut-off, we provide an automated literature-tracking workflow built with GitHub Actions. The bot continuously discovers recent work related to the LLM data lifecycle, filters duplicates, assigns candidates to the operation-centered taxonomy, and proposes updates through pull requests for human review.

The automation is designed to assist curation rather than replace it: newly discovered papers are never auto-merged into the curated list.

How it works

Recent arXiv papers
        ↓
Topic-specific query families
        ↓
Date / category / LLM-data relevance filtering
        ↓
README + historical-database deduplication
        ↓
Operation-centered taxonomy classification
        ↓
Primary tier + optional cross-tier role
        ↓
Generated Markdown update
        ↓
GitHub Pull Request
        ↓
Human review → merge

The classifier follows the same placement principle as the survey:

  • Data Substrates — data-bearing artifacts, benchmarks, trajectories, and executable environments.
  • Data Creation and Selection — annotation, synthesis, transformation, filtering, and model-aware selection.
  • Data Ingestion Strategies — organization, mixing, curriculum, replay, retrieval, search, decoding, and verification.

Because the unit of analysis is the operation rather than the paper as a whole, the bot can also flag cross-tier papers. For example, a method may generate or filter supervision in Tier 2 and immediately consume that supervision during optimization in Tier 3.

Two update modes

ModePurposeOutput
Weekly literature updateDiscover newly released papers on a rolling windowUpdates the bot-maintained recent-paper block and opens a PR
Historical backfillScan an exact date range, e.g. 2026-07-01 → 2026-08-17Generates an independent Markdown report under updates/ and opens a PR

The historical mode is useful when the repository has not been updated for a period of time or when a new query family is introduced and earlier papers need to be recovered.

Repository automation

The implementation lives in:

.github/workflows/
├── update-papers.yml       # scheduled / manual weekly update
└── backfill-papers.yml     # exact-date historical scan

scripts/
└── paper_bot.py            # fetch → filter → deduplicate → classify → render

config/
└── paper_bot.yaml          # search queries, taxonomy keywords, thresholds

data/
└── papers.json             # persistent bot-curated paper history

The automatically maintained README block is bounded by:

<!-- AUTO-LITERATURE:START -->
## Recent Automatically Discovered Papers

> This section is generated by the weekly literature bot and reviewed through pull requests before merge.
> Last generated: **2026-08-24** · Showing up to **30** recent papers.

### Data Substrates

- **[Benchmarking Patent Drafting from Inventor-Style Disclosures](http://arxiv.org/abs/2608.21249v1)** — Lekang Jiang et al. (2026). *Other*
- **[Enhancing LLMs in Predictive Political QA with Semi-Structured Data](http://arxiv.org/abs/2608.21218v1)** — Yinan Liu et al. (2026). *Other*
- **[Designing a Robust LLM-Based Evaluation System for Agentic AI in Drug Discovery Through Human Alignment](http://arxiv.org/abs/2608.21057v1)** — Emma Granqvist et al. (2026). *Other*
- **[MigrationNarrate: A Dataset for Detection of Migration Narratives in YouTube Videos](http://arxiv.org/abs/2608.20984v1)** — Fatima Haouari et al. (2026). *Other*
- **[VortexChat: An agentic framework for autonomous multi-objective integrated photonic design](http://arxiv.org/abs/2608.20688v1)** — Faqian Chong et al. (2026). *Other*
- **[ARQ: Agentic CodeQL Query Refinement for C/C++ Vulnerability Detection](http://arxiv.org/abs/2608.20637v1)** — Chunyi Wang et al. (2026). *Other*
- **[Weighted Memory Tree: Remembering What Matters for Long-Horizon LLM Agents](http://arxiv.org/abs/2608.20631v1)** — Quang Dao et al. (2026). *Other*
- **[ConceptGuard: Benchmarking Context-Sensitive Unlearning in Large Language Models](http://arxiv.org/abs/2608.20338v1)** — Sahil Kale et al. (2026). *Other*
- **[From Agent Behaviour to Agent-Friendly Documentation: An Empirical Study of How Coding Agents Discover, Read, and Write Technical Documentation](http://arxiv.org/abs/2608.20195v1)** — Zhijun Gao et al. (2026). *Other*
- **[OenoBench: A Wine-Domain Benchmark for Knowledge-Grounded Evaluation of Large Language Models](http://arxiv.org/abs/2608.20106v1)** — Nikita Khudov (2026). *Other*

### Data Creation and Selection

- **[Target-Aware Calibration Data Selection for Preserving Uncertainty in Quantized Language Models](http://arxiv.org/abs/2608.21019v1)** — Zhen Yang et al. (2026). *Data Selection*
- **[An Agentic Approach for Active Data Collection, Travel Behavior Modeling, and Weather-Sensitive Demand Prediction](http://arxiv.org/abs/2608.20320v1)** — Narges Ahmadi et al. (2026). *Annotation / Processing*

### Data Ingestion Strategies

- **[Beyond Fault Localization: A Trajectory-Level Study of LLM Agents for Microservice Root Cause Analysis](http://arxiv.org/abs/2608.21310v1)** — Qisheng Lu et al. (2026). *Runtime Retrieval / Search / Verification*
- **[EnSI-RAG: Entity-Structure-Indexed Retrieval-Augmented Generation for Long-Document Question Answering](http://arxiv.org/abs/2608.21252v1)** — Xuanyu Meng et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Specification Portability Across LLM Development Agents: Cross-Agent Compatibility in Specification-Driven Software Migration](http://arxiv.org/abs/2608.21208v1)** — Oleg Grynets et al. (2026). *Runtime Retrieval / Search / Verification*
- **[ReFrame: Evidence-Guided Test-Time Safety Alignment in Multimodal Large Language Models](http://arxiv.org/abs/2608.21100v1)** — Wenzheng Jiang et al. (2026). *Runtime Retrieval / Search / Verification* · _Cross-tier: Data Substrates_
- **[Trustworthy RAG: An Evaluation Agent for Detecting Misinformation and Knowledge Poisoning in Generative AI Systems](http://arxiv.org/abs/2608.21095v1)** — Balkrishna Giri et al. (2026). *Runtime Retrieval / Search / Verification*
- **[$Z^2$-ACT: End-to-End Verifiable Agentic Intent Control for Open 6G RAN](http://arxiv.org/abs/2608.21049v1)** — Sunder Ali Khowaja et al. (2026). *Runtime Retrieval / Search / Verification*
- **[UpgradeBench: A Decision-Centric Benchmark for Upgrading Fine-Tuned LLM Specialists](http://arxiv.org/abs/2608.20918v1)** — Ye Chen et al. (2026). *Curriculum / Mid-Training / Replay*
- **[TRACE: Agentic Catalog Enrichment with Multi-source Evidence Grounding](http://arxiv.org/abs/2608.20844v1)** — Rohan Kumar et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Knowing but Not Saying: Preventing Factual Access Failures in LLM SFT via Recall-Anchored Distillation](http://arxiv.org/abs/2608.20794v1)** — Haodong Chen et al. (2026). *Curriculum / Mid-Training / Replay*
- **[Vis-Poison: Poisoning Visual Knowledge in Multimodal Retrieval-Augmented Generation](http://arxiv.org/abs/2608.20756v1)** — Rujin Liang et al. (2026). *Runtime Retrieval / Search / Verification*
- **[AsmEvo: Agentic Assembly-Level Optimization of AMD GPU Kernels with Functional Equivalence Verification](http://arxiv.org/abs/2608.20711v1)** — Ji Liu et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Towards Faithful Simulation of Human Shopping Behavior](http://arxiv.org/abs/2608.20707v1)** — Jiakai Tang et al. (2026). *Runtime Retrieval / Search / Verification*
- **[JuryProbe: An Empirical Consensus-Risk Diagnostic for Routing Reference-Free Factuality Judge Panels to Grounded Verification](http://arxiv.org/abs/2608.20607v1)** — Tianxin Zhou et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Terminal Agents: A Survey of AI Agents in Command-Line Environments](http://arxiv.org/abs/2608.20485v1)** — Yi Bin et al. (2026). *Runtime Retrieval / Search / Verification*
- **[MidTool: Mid-training Data Synthesis for Agentic Tool Use](http://arxiv.org/abs/2608.20314v1)** — Fengqing Jiang et al. (2026). *Curriculum / Mid-Training / Replay* · _Cross-tier: Data Creation and Selection_
- **[Inject, Align, Recover: Staged Post-Training for Retrieval-Free Document Knowledge Internalization](http://arxiv.org/abs/2608.20281v1)** — Qian Kou et al. (2026). *Runtime Retrieval / Search / Verification*
- **[Decoding silent reading from non-invasive EEG](http://arxiv.org/abs/2608.20186v1)** — Ingo Marquardt et al. (2026). *Runtime Retrieval / Search / Verification*
- **[FormalTCS: Benchmarking End-to-End Frontier Formal Theoretical Computer Science Research of Large Language Models](http://arxiv.org/abs/2608.20153v1)** — Dingzirui Wang et al. (2026). *Runtime Retrieval / Search / Verification*

<!-- AUTO-LITERATURE:END -->

so the workflow never rewrites the manually curated core of this repository.

Curation policy

Automation is intentionally conservative:

  1. Discovery is automatic; acceptance is human-reviewed.
  2. Existing README entries and previously accepted bot records are deduplicated before proposal.
  3. The workflow prefers high-recall discovery followed by stricter relevance and taxonomy filtering.
  4. Ambiguous methods may receive a primary tier plus a cross-tier label.
  5. Important accepted papers can later be moved from the automatically maintained recent-paper block into the main curated sections.

This makes the repository a living companion to the survey while preserving the quality and interpretability of the manually curated taxonomy.


Scope and Update Policy

  • Survey literature cut-off: June 2026.
  • Repository status: living resource; a GitHub Actions literature bot tracks new candidate papers beyond the paper cut-off, with all additions reviewed through pull requests.
  • In scope: work where data resources, data construction/selection, information scheduling, retrieval, verification, trajectories, or executable environments play a substantive role in LLM development or evaluation.
  • Out of scope by default: architecture-only or optimization-only papers where the data lifecycle is incidental.
  • Source preference: primary papers, official project pages, ACL Anthology, OpenReview, arXiv, or official dataset/model repositories whenever available.

2026 coverage highlights

Recent additions reflected in the survey/repository include:

  • Research-level reasoning data: ResearchMath-14K.
  • Real and executable coding-agent data: Multi-SWE-bench, SWE-Chat, SWE-RL, SWE-Playground.
  • Tool-agent trajectories and environments: TOUCAN, FunReason-MT, UniToolCall, WebWorld, ClawGym.
  • Environment/data co-evolution: Agent-World, Nex-N1, ClawEnvKit, AgentFrontier.
  • Recent survey context: Agentic Tool Use in LLMs, Agentic Environment Engineering, and The LLM Data Auditor.

Contents

1. Surveys

Data Selection

Generation

Blogs

2. Taxonomy

We organize the LLM data lifecycle through an operation-centered, three-tier taxonomy. The goal is not merely to separate training stages, but to distinguish what information-bearing objects exist, how their content or membership is changed, and how available information is presented to and consumed by the model.

TierOperational questionScopeRepresentative examples
Tier 1: Data SubstratesWhat information-bearing artifacts or environments are available?Corpora, instruction/preference data, benchmarks, reasoning/code resources, trajectories, executable environmentsPretraining corpora, SFT/RL data, math/code benchmarks, tool-use trajectories, agent environments
Tier 2: Data Creation and SelectionWhat supervision exists, and how is it created or modified?Annotation, synthesis, transformation, filtering, diversity/quality/model-aware selectionDistillation, self-instruct, back-translation, symbolic generation, data filtering, influential-data selection
Tier 3: Data Ingestion StrategiesHow, when, how often, and under what context is information consumed?Packing, contextual conditioning, mixture weighting, curriculum, annealing, replay, retrieval, search, decoding, verificationSample construction, data mixing, mid-training, multi-stage curricula, RAG, test-time search

Placement rule. Tier 2 changes the supervision or data artifacts that exist; Tier 3 changes how available supervision or information is delivered to and consumed by the model. For example, offline data selection is primarily Tier 2, whereas dynamic data mixing is Tier 3. An agent trajectory is a Tier-1 substrate; generating or filtering trajectories is Tier 2; using them in iterative optimization or test-time interaction is Tier 3.

Cross-tier methods. The unit of analysis is the operation rather than the paper as a whole. Methods such as rejection-sampling fine-tuning or error-driven preference optimization can span multiple tiers: they may generate/filter supervision in Tier 2 and immediately consume the retained supervision during optimization in Tier 3.

3. Data Substrates

3.1 General Domain

3.1.1 Pretrain

3.1.2 SFT

3.1.3 RL

3.2 Specific Domain

3.2.1 Reasoning and Code

3.2.2 Safety and Alignment

3.2.3 Agent and Tool Use

3.3 Summary: Substrate Dynamics and Trade-offs

The substrate view highlights a shift from raw scale toward curated information density, and—especially for agents—from stored text/trajectories toward executable environments that can generate tasks, observations, failures, recovery paths, and verification signals on demand.

4. Data Creation and Selection

4.1 Annotation

4.1.1 Data Processing

4.1.2 Prompt Engineering

4.2 Synthesis

4.2.1 Sampling-Based

4.2.2 Data Transformation

4.2.3 Back-Translation

4.2.4 Human-AI Collaboration

4.2.5 Symbolic Generation

4.3 Selection

4.3.1 Diversity

4.3.2 Quality

4.3.3 Composite Strategy

4.4 Summary: Creation and Selection Trade-offs

Across creation and selection methods, the survey highlights three recurring transitions: teacher distillation → autonomous/self-play generation, static quality filtering → model-conditional utility, and stored examples → verifier-grounded or environment-generated supervision. Selection and synthesis increasingly interact through closed loops rather than remaining independent preprocessing stages.

5. Data Ingestion Strategies

5.1 Efficiency & Effectiveness

5.1.1 Sample Construction

Cross-tier note: this section focuses on the ingestion/optimization-time role of sample construction. Methods that generate persistent new supervision (e.g., rejection sampling or targeted error injection) also have a Tier-2 creation component.

5.1.2 Sample Mixing

5.2 Training Pipeline Optimization

5.2.1 Mid Training

5.2.2 Multi-Stage Training

5.3 Capability Alignment Strategies

5.3.1 Constraint

5.3.2 Cognitive Alignment

5.4 Truthfulness & Consistency

5.4.1 Consistency

5.4.2 RAG

5.4.3 Decoding

5.5 Summary

Data ingestion spans both training-time scheduling and runtime information use. Training-time methods determine how supervision is organized, weighted, ordered, replayed, or conditionally presented; runtime methods determine when self-generated or external evidence is retrieved, searched, decoded, or verified.

6. Cross-Tier Synthesis

The lifecycle view exposes several recurring transitions that are less visible when datasets, synthesis, selection, training schedules, and agent systems are studied separately:

  1. Static data quality → model-conditional utility. Data usefulness increasingly depends on the target model's current loss, confidence, errors, capability state, and learnability frontier.
  2. Instance-level annotation → system-level specification and verification. As synthesis becomes more autonomous, human effort shifts toward task specification, verifier design, environment construction, governance, and exception handling.
  3. Stored artifacts → executable data-producing environments. Agentic data increasingly includes environments that generate tasks, actions, observations, failures, recovery trajectories, and reward signals on demand.
  4. Offline data preparation → adaptive runtime information acquisition. Retrieval, search, verification, and test-time compute extend data optimization beyond parameter training.

These trends motivate treating data engineering as the joint design of artifacts, transformations, and adaptive information-use policies.

7.1 Data Resources and Governance

7.1.1 Domain-Specific Data Scarcity

7.1.2 Cross-Domain Data Reutilization

7.1.3 Data Sensitivity and Privacy

7.2 Data Creation and Selection

7.2.1 Agentic Data Pipelines and Closed-Loop Flywheels

7.2.2 Multi-source Synthesis

7.2.3 User Collaboration

7.2.4 Cross-modal Knowledge Utilization

7.2.5 Data Efficiency

7.2.6 Length-Aware Data Synthesis and Selection

7.2.7 Model-Aware Filtering

7.3 Data Ingestion Strategies

7.3.1 Unified Post-Training

7.3.2 Cross-Stage Data Reutilization

7.3.3 Data Unlearning

7.3.4 Test-Time Strategy

Citation

If you use this repository or the taxonomy in your research, please cite the accompanying survey:

@article{rao2025datacentric,
  title   = {A Data-Centric Perspective on the Lifecycle of Large Language Models},
  author  = {Rao, Jun and Liu, Xuebo and Yan, Haotian and Shen, Junjie and Mo, Haosi and
             Dong, Yanghaopeng and Yan, Zihao and Wang, Ziyi and Lin, Zepeng and Meng, Xiaojun and
             Yu, Zixiong and Deng, Liqun and Wei, Jiansheng and Wang, Yunhe and Zhang, Min},
  journal = {TechRxiv},
  year    = {2025},
  doi     = {10.36227/techrxiv.176620610.03288677/v1},
  url     = {https://doi.org/10.36227/techrxiv.176620610.03288677/v1}
}

For GitHub-native citation support, we also recommend adding a CITATION.cff file to the repository root.

Contributing

Contributions are welcome. Please open an issue or pull request to add a paper, dataset, benchmark, correction, or missing link.

To keep the list consistent:

  1. Use primary sources whenever possible — official paper, ACL Anthology, OpenReview, arXiv, or official project page.
  2. Place resources by operation, not only by training stage or application domain.
  3. Use cross-tier notes when needed. A method may appear under the tier corresponding to the operation being discussed while retaining a secondary role elsewhere.
  4. Avoid duplicates. Prefer the formally published version over an arXiv duplicate when both are available.
  5. Keep entries concise: Title — venue/year — link.
  6. For new 2026+ work, briefly explain why it changes or extends the taxonomy when the placement is non-obvious.

Suggested pull-request title:

[Add] <Paper / Dataset / Benchmark Name> → <Section>

Acknowledgements

We thank the authors of the papers, datasets, benchmarks, and open-source resources collected here, as well as community contributors who help keep the list accurate and up to date.


Data is not only what a model trains on — it is also what gets created, selected, scheduled, retrieved, verified, and regenerated throughout the model lifecycle.

Contributors

raojay7

155 commits

hiterlink

55 commits

chris13798

16 commits

luakcoder

15 commits

Languages

Python

100.0%