--- pretty_name: Nemotron-Math-Proofs-v3-SFT language: - en license: - cc-by-4.0 task_categories: - text-generation tags: - math - proofs - mathematical-reasoning - text - human - synthetic - automated - post-training - Nemotron_3_Ultra size_categories: - 100K` markup in visible answer text. Proof and refinement samples must contain non-empty visible `Solution` and `Self Evaluation` sections. Verification and meta-verification samples must contain a parseable final score and use the visible final proof rather than a scratchpad as input. After final quality filtering, the verification subset contains 117,622 score-`0` traces and 118,738 score-`0.5` or score-`1` traces. #### Dataset Fields The released dataset contains the following fields: * `uuid`: Unique identifier for the sample. * `messages`: Standardized user/assistant message sequence for LLM training. Assistant messages contain visible `content` and the corresponding long-form `reasoning_content`. * `tools`: Tool definition list, if any. * `license`: Per-sample license label. The released samples use `cc-by-4.0`. * `metadata`: Task metadata, including `problem`, `problem_idx`, `data_type`, recorded input and generated token counts, and optional round or stage information. * `source`: Source label for the seed problem. The released samples use `AoPS`. * `dataset`: Dataset/release label. The released samples use `Nemotron-Math-Proofs-v3-SFT`. * `subset`: Compatibility subset label. Use `metadata.data_type`, not this field, to identify the task type. * `filter_reason`, `processing_info`, `match_contexts`, and `matched_categories`: Post-processing and compatibility fields retained by the release pipeline. The authoritative task type is `metadata.data_type`, with one of the following values: `proof`, `refinement`, `verification`, or `meta_verification`. #### Data Collection Method * Hybrid: Manually-Collected, Synthetic, Automated #### Labeling Method * Hybrid: Manually-Labeled, Synthetic, Automated ## Dataset Format * **Modality:** Text * **Format:** JSONL * **Structure:** JSONL records with natural-language proof problems and generated proof, refinement, verification, or meta-verification traces. * **Files:** The `train` split is stored as 10 JSONL shards, `data/train-00000-of-00010.jsonl` through `data/train-00009-of-00010.jsonl`. Concatenating the shards in order reproduces the original single file byte for byte; `load_dataset` reads them as one split. ## Dataset Quantification Subset Samples: | Split | `metadata.data_type` | Samples | Average Generated Tokens | |---|---|---:|---:| | train | proof | 58,543 | 210,267 | | train | refinement | 67,971 | 208,965 | | train | verification | 236,360 | 41,361 | | train | meta_verification | 52,016 | 29,057 | | train | Total | 414,890 | 91,110 | Source Pool: 15,879 problems Unique Problems Represented After Filtering: 15,818 Total Disk Size: 121.95 GiB (130,940,075,840 bytes) Recorded Generated Token Count: 37,800,710,874 Estimated Input Token Count: 1,246,480,841 Total Recorded Token Count: 39,047,191,715 Generated token counts are taken from the inference metadata. Input token counts are pipeline estimates based on prompt text length rather than a tokenizer re-count. ## Reference(s): * [An Open Recipe for IMO Gold: Training Nemotron for Olympiad Mathematics](https://arxiv.org/abs/2609.10712) (technical report) * [DeepSeek-V4-Pro](https://huggingface.co/deepseek-ai/DeepSeek-V4-Pro) * [nvidia/Nemotron-Math-Proofs-v1](https://huggingface.co/datasets/nvidia/Nemotron-Math-Proofs-v1) * [nvidia/Nemotron-Math-Proofs-v2](https://huggingface.co/datasets/nvidia/Nemotron-Math-Proofs-v2) * [DeepSeekMath-V2: Towards Self-Verifiable Mathematical Reasoning](https://arxiv.org/abs/2511.22570) * [Nemotron-Math paper](https://arxiv.org/abs/2512.15489) * [NeMo-Skills](https://github.com/NVIDIA/NeMo-Skills) * [Nemotron-MathProofs-v1 documentation](https://nvidia-nemo.github.io/Skills/releases/nemotronmathproofs/) ## Ethical Considerations: NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. Developers should work with their internal developer teams to ensure this dataset meets requirements for the relevant industry and use case and addresses unforeseen product misuse. Please report quality, risk, security vulnerabilities or NVIDIA AI Concerns [here](https://www.nvidia.com/en-us/support/submit-security-vulnerability/).