Middle East & North Africa · Arabic / Latin
Kurdish Multilingual Speech Dataset
Kurdish multilingual speech sourced to your specification — no inventory, no fixed listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.
Why multilingual speech in Kurdish is its own problem
For Kurdish the multilingual problem is internal. Kurmanji and Sorani are treated as one language by buyers but behave as two: they do not cross-communicate, their grammars differ, and their annotators are not interchangeable — a Sorani team cannot check Kurmanji output. A project that pools them under one Kurdish label produces a set whose quality cannot be audited, because the only people who could audit half of it were never hired. The state languages add a second layer, since speakers from each of the four countries bring a different one into the recording.
The field to pin down first: Hours, speaker counts, and recording conditions are listed per branch, and the two branches are annotated and delivered by separate teams with separate quality reports, never merged into one figure.
At a glance
| Language | Kurdish |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic / Latin |
| Category | Multilingual Speech |
| Specification field to settle first | Hours, speaker counts, and recording conditions are listed per branch, and the two branches are annotated and delivered by separate teams with separate quality reports, never merged into one figure. |
| Delivery | Sourced to order, pilot batch before the full run |
What multilingual speech data is
Speech data covering multiple languages within one project, used for multilingual ASR, cross-lingual transfer, and language identification.
What buyers get wrong about it
The biggest risk in a multilingual project is uneven quality — annotation teams for different languages work to different standards, and once merged they drag each other down.
The specification field that decides the quote
Speaker count, hours, and recording conditions must be listed per language; a combined total does not cut it.
The language side: what Kurdish demands
The two main branches of Kurdish (Sorani and Kurmanji) have low mutual intelligibility, close to two separate languages, and they use different scripts. Public resources are so thin that even TTS datasets are rare — a textbook scarce language.
What we can put in this delivery
-
Read and conversational speech
Scripted recording for TTS, and unscripted conversation for recognition. Specified separately because they need different speaker pools.
-
Transcription to your convention
Orthographic or phonetic, with the guideline written before production and shared with you for review.
-
Speaker metadata
Age band, gender, region and dialect background per file, so you can slice the dataset rather than take it whole.
-
Consent documentation
Signed speaker consent covering the intended use, plus collection methodology and the annotation guideline.
-
Pilot batch
A small batch first, which you can reject. Misalignments surface after a few hours rather than at delivery.
-
Delivery in your format
Audio format, sampling rate, segmentation length and metadata schema set to your pipeline's requirements.
What arrives in a delivery
| Component | What it is |
|---|---|
| Audio files | Format, sampling rate and segmentation length set to your pipeline. Named to a convention you specify. |
| Transcription | Orthographic or phonetic, produced under a guideline you review before production starts. |
| Speaker metadata | Age band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced. |
| Recording conditions | Environment, device and, where relevant, measured signal-to-noise ratio per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed speaker consent covering your intended use, with the transfer mechanism addressed where required. |
| Collection methodology | How speakers were recruited, screened and scheduled — the part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Questions we get about Kurdish Multilingual Speech
How many distinct speakers can you provide for Kurdish Multilingual Speech?
It depends on the specification and the timeline, and we will give a real number rather than a target. For this pairing, speaker recruitment is usually the step that sets the schedule. Hours, speaker counts, and recording conditions are listed per branch, and the two branches are annotated and delivered by separate teams with separate quality reports, never merged into one figure.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. For Kurdish the multilingual problem is internal. That is exactly the kind of decision a default guideline leaves open, and it is where annotators diverge. Send us your guideline, or we will draft one and you can review it before production starts.
Do you offer a sample before we commit to a full run?
Yes. Select a free sample in the request form and describe what you need. A pilot batch is the cheapest way to establish whether the quality bar is reachable for Kurdish Multilingual Speech before committing to the full volume.
Is the data licensed or owned outright?
Licensing terms are set per project, so tell us how the model will be used and whether it will be distributed. Consent documentation travels with the data either way, and we do not handle medical or clinical data or recorded telephone calls.
Other datasets in Kurdish
-
Kurdish Voice Assistant
Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.
-
Kurdish Elderly Voice
Speech data from elderly speakers, usually stratified by age band and health status, used for voice products built for older users.
-
Kurdish Accented English
English speech from non-native speakers or specific regional accents, grouped by accent origin, used to improve accent robustness in ASR.
-
Kurdish Speech Translation
Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.
-
Kurdish In-the-Wild Speech
Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.
-
Kurdish Call Center Speech
Recorded customer-service calls, real or simulated, capturing both the agent and the caller side, used for call center QC, intent recognition, and dialogue systems.
Multilingual Speech in other languages
-
Amharic Multilingual Speech
Sub-Saharan Africa
-
Ukrainian Multilingual Speech
Europe
-
Swahili Multilingual Speech
Sub-Saharan Africa
-
Hausa Multilingual Speech
Sub-Saharan Africa
-
Uzbek Multilingual Speech
Central Asia & Caucasus
-
Hindi Multilingual Speech
South Asia
Request Kurdish Multilingual Speech
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline — not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.