Datuva by Zovda · Training data

LLM training data, built to a documented standard.

20 corpus collections across video, audio, image–text pairs, question banks, and code-agent tasks. Prepared for continued pre-training, multimodal alignment, SFT, RL, and evaluation. Scope is confirmed before delivery; sample packs and data cards are shared after review.

  • 20 corpus collections
  • 5 corpus families
  • Reply within 1 business day
What we supply

Five corpus families. One delivery standard.

20 collections today, each shipped with a manifest, a data card, and a field schema.

01 · Video & multimodal

Video & multimodal

Short-video, branded video, vlog, 4K stock and camera-movement footage, sports video with three-level temporal annotation, 4K game screenshots, egocentric sessions with seven annotation types, and video SFT clips — each item with structured metadata.

02 · Question banks

Question banks & reasoning

Nine subjects across primary, middle, and high school, plus 16 vocational exam categories. Every item carries stem, options, answer, worked solution, and knowledge point.

03 · Code & agents

Code & agent trajectories

Repository-level tasks: one open-source issue per package, with a runnable sandbox image, reference patch, test patch, and an automatic grading script.

04 · Structured SFT

Structured SFT & image–text

E-commerce image–text pairs and attribute-extraction SFT records with field-level evidence chains. The current release holds 2,808 records.

05 · Audio

Audio

Music stems split by instrument — lead vocal, harmony, accompaniment — delivered as track-organized WAV sets, including a full 41-stem reference track.

Catalogue map

Two ways to read the catalogue.

Sort by modality, then by training stage: the same 20 collections, one catalogue, two views.

ModalityContinued pre-training & alignmentSFTRL & agentsEvaluation
Text · question banks—9 subjects across three school stages and 16 vocational categories with worked solutions; attribute extraction with evidence chains—Held-out question sets
Image–textE-commerce pairs with attributes and titlesAttribute extraction with field-level evidence chains——
Image———4K game screenshots for art-style checks
VideoShort-video, branded, vlog, 4K and camera-movement footage; egocentric sessions with seven annotation typesVideo-understanding SFT clips—Held-out clips with reference labels
AudioInstrument-split stems — vocal, harmony, accompaniment — as track-organized WAV———
Code · agents—Issue-to-patch trajectories with reference patchesSandboxed tasks with automatic gradingAutomatic grading scripts

Swipe sideways for every stage →

Production

How a corpus is produced.

Five steps from scope confirmation to signed delivery.

1

Scope

Confirm collection, volume, schema, and delivery format.

2

Intake

Register raw files, IDs, versions, and integrity checks.

3

Processing

Parse, clean, annotate, and structure to the agreed schema.

4

Quality check

Technical validation, content sampling, cross-field consistency.

5

Versioned delivery

Data, manifest, checksums, and acceptance records.

Delivery

One structure per collection.

Scope, volume, format, and timeline are confirmed per project.

ItemWhat ships
manifest.jsonEvery file with name, size, date, and collection ID.
UTF-8 JSONLOne record per line for text and annotations.
Media filesOriginal-resolution video and audio, plus proxy files for review.
Packaged tasksdocker/ (OCI layout) and json/ (task, patches, grading script).
DocumentsData card, field schema, and a PDF spec for each collection.
Product facts

Current delivery scope.

Parameters not yet fixed are confirmed against your project scope.

20corpus collections
5corpus families
9 subjects × 3 school levelsquestion banks
16vocational exam categories
2,808attribute-extraction SFT records
1 business dayreply time
Request access

Request the corpus catalog.

Tell us the modality, training stage, and volume. We reply within one business day. Sample packs, data cards, and field schemas are shared after your request is reviewed.

Access is activated after scope confirmation.

FAQ

Before you request a corpus.

Can we start with a smaller scope?

Yes. Most projects start with one collection or one modality, then extend after acceptance.

How do we review a corpus before committing?

After the scope conversation we share a sample pack, the data card, and the field schema.

Is each collection a ready-to-use LLM dataset?

Each collection is delivered as a structured dataset with a fixed schema. Format and volume are confirmed for your project.

Can a collection be adapted?

Annotation schema, sampling, and delivery format can be adjusted to your pipeline.

Do you build new collections?

Yes. We scope new collections with the same production process before quoting.