.txt file of raw text in one of two shapes:
- Pretraining — the whole file is plain text.
- Instruction tuning (SFT) — one line of the form
prompt<TAB>completion. Everything before the first tab is the prompt, everything after is the completion.
Folder layout
- The folder is named
texts(raw text) and sits next to the manifest CSV. - UTF-8 encoded. Every file must end in
.txt. The ingestor also accepts.text, but training opens only<filename>.txt, so a.textdataset ingests and then fails to train.
Manifest CSV
There is no label column. Setting
label: in ingest.yaml is rejected.
Ingest with the CLI
Each split is one folder laid out as above. Ingest the training and the test split separately:--label-column: the CLI rejects it for this task because it trains on the text itself.
ingest.yaml
What the ingestor checks
Plus the checks every ingest runs, except label diversity (no label). No tokenizer is needed at ingest; the ingestor records a data-derived text profile (script mix and length distribution, never the text) for the platform’s tokenizer-fit warning.
Sample dataset
The template ships five files: three plain-text passages and twoprompt<TAB>completion pairs, with a five-row manifest. The manifest ships as labels_file_sample.csv: rename it to labels.csv before you ingest the folder, because the CLI reads only that name. For the Helm chart, stage the renamed folder so that it matches the paths in the ingest.yaml above.
Score formulas
When you define a use case on this data, the platform currently accepts Accuracy and Perplexity.Next steps
- Ingest the data: Prepare Data
- Shared rules for every template: Dataset templates