Skip to main content
Predict masked-out words. This task is self-supervised: there is no label — the training side masks tokens on the fly. Each sample is one .txt file holding a space-separated token sequence, listed in a manifest CSV.

Folder layout

  • The folder is named sequences (not texts) — the ingestor reserves sequences/ for pre-tokenized data — and sits next to the manifest CSV.
  • One sequence per file, tokens separated by spaces, UTF-8 encoded. Every file must end in .txt. The ingestor also accepts .text, but training opens only <filename>.txt, so a .text dataset ingests and then fails to train. Example from the shipped sample: Lepirudin indication Huntington phenotype_present Chorea associated_with Dystonia.
  • The shipped sample also contains a tokenizer.json next to the CSV. The current ingestor neither reads nor copies it; it is part of the sample only.

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:
Do not pass --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). For text tasks the ingestor also records a data-derived text profile — Unicode-script mix and document-length distribution, never the text itself — so the platform can warn when a model’s tokenizer is a poor fit for the dataset.

Sample dataset

The template ships five knowledge-graph random-walk sequences and 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 Masked Token Accuracy and Perplexity.

Next steps