Middle East & North Africa · Arabic / Latin
Kurdish Multilingual Speech Dataset
Kurdish Multilingual Speech delivered to your specification. A catalog entry, not a stock 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
-
Collection to your specification
Scripted or unscripted, in the language, domain and conditions your task needs. Specified separately where the variants need different contributor pools.
-
Labels to your convention
Orthographic, phonetic or categorical, with the guideline written before production and shared with you for review.
-
Contributor metadata
The attributes that let you slice the set rather than take it whole. The ones your task turns on, not a fixed list.
-
Consent documentation
Signed contributor 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
File format, structure, segmentation and metadata schema set to your pipeline's requirements.
What arrives in a delivery
| Component | What it is |
|---|---|
| The data files | Format, structure and segmentation set to your pipeline. Named to a convention you specify. |
| Labels or transcription | Orthographic, phonetic or categorical, produced under a guideline you review before production starts. |
| Contributor metadata | The attributes that let you slice the set: age band, gender, region, dialect background, or whatever your task turns on. |
| Collection conditions | Environment, device and, where it can be measured, signal quality: recorded per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed contributor consent covering your intended use, plus cross-border transfer terms where they apply. |
| Collection methodology | How contributors 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 Dataset
How many distinct speakers can you provide for Kurdish Multilingual Speech Dataset?
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 Dataset 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
Customer-service calls, simulated rather than intercepted, capturing both the agent and the caller side, used for call center QC, intent recognition, and dialogue systems.
Request Kurdish Multilingual Speech Dataset
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.
- You send the spec Language, hours, recording conditions, and the deadline.
- We reply within two business days A real number and a real timeline, not a range.
- You approve a pilot batch A small run first, so problems surface before the full order.
- Full run, then delivery with documents Audio, transcripts, and the consent record for every speaker.