AIAny
Icon for item

Nemotron Image Training v3

Collection of 76 image-centric multimodal subdatasets (≈6.9M samples, ~39.56B estimated tokens) for training vision–language models, each published with a standardized conversation JSONL and dataset card. Media are referenced by path/URL and must be fetched separately; licensing is primarily CC-BY-4.0 with per-subdataset variations.

Introduction

Nemotron Image Training v3 targets large-scale vision–language training workflows by bundling 76 focused subdatasets into a single, standardized release. Rather than supplying pixels inline, each subdataset ships a Megatron/Megatron-Energon–compatible conversation JSONL and a README describing upstream media sources, licensing, and the expected local layout—so the main deliverable is curated, model-ready multimodal supervision with explicit provenance and labels.

What Sets It Apart
  • Broad, task-focused coverage: the collection spans QA, OCR, grounding, multi-image reasoning, chart/plot QA, and more, enabling unified training for diverse VLM capabilities rather than a single benchmark. This makes it easy to assemble mixed curricula (e.g., OCR-heavy + reasoning-heavy mixes) without reinventing formatting.
  • Large but modular: ~6.9M rows and an estimated 39.56B tokens distributed across 76 subdatasets (approx. 9.25 TB referenced media). Each subdataset includes a dataset card and a conversation JSONL, so you can pick only the subsets you need and reproduce the original media layout.
  • Labeling & verification transparency: data are a hybrid of human and synthetic sources, with model-labeling and verification passes noted per-subdataset (e.g., qwen/gemini/gpt labels), and clear license statements (mainly CC-BY-4.0 with a few GPL/BSD/CC BY-SA exceptions).
Who It’s For & Tradeoffs

Great fit if you need: curated multimodal supervision to pretrain or fine-tune VLMs at scale; modular subdatasets for targeted curricula; Megatron/Megatron-Energon–style JSONL ingestion. You get standardized conversational examples and provenance metadata, which reduces preprocessing friction. Look elsewhere if: you need datasets with embedded pixels (this release references upstream media only), if strict end-to-end commercial clearance is required for every sample (some subdatasets carry differing upstream licenses), or if you require uniformly human-verified labels—quality and label provenance vary by subset.

Practical Notes
  • Owner/publisher: NVIDIA Corporation; first published 2026-04-28. License: primarily CC-BY-4.0, with specific subdataset exceptions (e.g., ChartQA labels under GPL-3.0; zhwiki includes CC BY-SA / GFDL constraints). Always consult each subdataset README before commercial use.
  • Integration: JSONL format is compatible with Megatron-Energon loaders; media must be downloaded & arranged locally as described in each README so paths resolve at training time.
  • Resource planning: referenced media volume is substantial (≈9249.07 GB); plan storage and data-access bandwidth accordingly.

Overall, v3 is a practical, modular package for teams building or scaling vision–language training pipelines where explicit media provenance, per-subdataset licensing, and standardized multimessage JSONL formatting matter more than immediate pixel availability.

Information

  • Websitehuggingface.co
  • AuthorsNVIDIA Corporation
  • Published date2026/04/28

Categories

More Items

Hugging Face

A collection of ready-to-run Hugging Face Jobs OCR scripts that add a markdown column (or structured JSON) to image datasets, with model switching, layout detection, server-mode serving, and per-model options for table/form extraction.

Hugging Face

Provides 115M public GitHub source files (≈873GB of code, ~1TB uncompressed) with per-file metadata (repo, path, language, license). Supports streaming, language/license filtering and full download for training and evaluating code LLMs and code generation models.

Hugging Face

Provides labeled prompts with full-reference answers (including chain-of-thought and code blocks) and per-example metadata to train edge routing/orchestrator models that decide whether to handle inputs locally or route them to larger models. Includes complexity scores, coding/math flags, routing justifications, and an automated override rule; suited for fine-tuning small models (50M–1.5B) for edge deployment.