.txt file with one line of the form source<TAB>target.
Folder layout
- The folder is named
textsand sits next to the manifest CSV. - Put exactly one tab between source and target: everything before the first tab is the source, everything after is the target. Nothing checks this structure: neither the CLI nor the ingestor looks for the tab, and training reads a file without one as a source with an empty target.
- 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).
Sample dataset
The template ships fivesource<TAB>target pairs (translation, summarization and paraphrase examples) 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 only.Next steps
- Ingest the data: Prepare Data
- Shared rules for every template: Dataset templates