--- language: - dv task_categories: - text-generation - text-classification pretty_name: Dhivehi Instruct v1 size_categories: - 10K"}, {"role": "assistant", "content": ""} ], "task": "headline | classification | continuation | transliteration", "instr_lang": "dv | en | latin", "template_id": "", "source_doc_id": "", "generator": "template", "meta": {} } ``` ## Sources - [d3b4g/dhivehi-corpus](https://huggingface.co/datasets/d3b4g/dhivehi-corpus) — Dhivehi news corpus (~430k docs) - [d3b4g/dhivehi-stories](https://huggingface.co/datasets/d3b4g/dhivehi-stories) — Dhivehi creative writing (~18k docs) ## Construction & Data Hygiene The build is fully seeded and reproducible. Key steps: 1. **Filter** — documents need ≥85% Thaana among their letters and 80–3,000 words. Excerpt-length documents (15–79 words) are admitted for the classification task only. 2. **Frozen holdout** — 5% of all filtered document IDs (22,248) are frozen *before* any rows are built. No training or validation row derives from a holdout document, and the publishing script hard-fails if any does. The holdout seeds a future **DhivehiEval** benchmark, giving this dataset a hard-enforced train/eval separation. 3. **One task per document** — each source document contributes to at most one task, preventing near-duplicate leakage (e.g. a headline row and a continuation row derived from the same article). 4. **Validation & dedup** — schema, length, and Thaana-ratio checks, followed by exact and MinHash near-duplicate filtering on outputs. Task-specific cleaning applied during validation: - **Cut-off removal:** Some source texts are scraped teasers that end mid-thought with an ellipsis (…). Rather than repair them, rows whose input ends this way are **dropped entirely** — the published data contains no ellipsis-truncated prompts. - **Script normalization:** Arabic ligatures embedded in Dhivehi text (e.g. ﷲ) are romanized in transliteration targets to their standard Latin forms (`allah`, or `abdhullah` when attached to a name stem), and Arabic punctuation is mapped to ASCII. Any sentence with a character the romanizer cannot fully convert is dropped, so no stray non-Latin glyphs survive in transliteration outputs. - **Clean outputs:** ASSISTANT responses contain strictly the requested output, with no conversational filler — optimal for programmatic evaluation and automated pipelines. ## Use Cases A foundational resource for downstream Dhivehi NLP, including: - **Instruction tuning** — teaching base models to follow Dhivehi instructions across classification, generation, and transliteration. - **Content categorization** — tagging local-language news, feedback, and unstructured business text using the balanced classification data. - **Accessibility & tooling** — leveraging the Thaana↔Latin transliteration pairs for text-to-speech front-ends, search, and reading assistants. ## Known Limitations - **Continuation flow:** Because outputs are the source document's real subsequent sentences, models trained on this subset may occasionally see abrupt topic transitions where the original article changed context. Evaluate generative output flow accordingly. - **Transliteration convention:** Outputs follow one common informal Malé Latin convention; Dhivehi romanization has no single standard, and other schemes exist. - **Classification labels** derive from publisher section metadata, which is noisy at the margins. - **Register skew:** the corpus is heavily news-weighted; the stories source provides the only substantial non-journalistic register. - No open-ended QA, summarization, or reasoning tasks yet — planned for v1.1 after a human-reviewed pilot. ## License and Intended Use Source texts are the copyright of their original publishers; this dataset is released for research use in Dhivehi NLP. If you are a publisher of source material and have concerns, please open a discussion on this repository.