Middle East & Europe · Latin
Turkish Speech Commands Dataset
Turkish speech commands 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 speech commands in Turkish is its own problem
Turkish command words generate a large number of variants through agglutinative suffixes (a verb root with different person and honorific endings). Users really do say all of those variants, but including every one makes the word list balloon, so the inclusion boundary has to be drawn first.
The field to pin down first: The inclusion boundary (roots only / common variants / everything) has to be locked, with a table of variant generation rules provided.
At a glance
| Language | Turkish |
|---|---|
| Primary region | Middle East & Europe |
| Writing system | Latin |
| Category | Speech Commands |
| Specification field to settle first | The inclusion boundary (roots only / common variants / everything) has to be locked, with a table of variant generation rules provided. |
| Delivery | Sourced to order, pilot batch before the full run |
What speech commands data is
Targeted recordings of short command words or phrases, usually with many speakers reading each entry several times over, used for wake words and on-device command recognition.
What buyers get wrong about it
What buyers consistently underestimate is the repetition count — a single command entry needs at least a few dozen distinct speakers, each reading it multiple times, to cover pronunciation variation.
The specification field that decides the quote
Once the word list is locked it cannot change; adding words midway means starting a new batch.
The language side: what Turkish demands
Turkish is an agglutinative language: one root can carry a long chain of suffixes, so the word list explodes. Istanbul and eastern accents also differ noticeably — if speaker origin is not recorded clearly, model generalization suffers.
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 Turkish Speech Commands
How many distinct speakers can you provide for Turkish Speech Commands?
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. The inclusion boundary (roots only / common variants / everything) has to be locked, with a table of variant generation rules provided.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. Turkish command words generate a large number of variants through agglutinative suffixes (a verb root with different person and honorific endings). 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 Turkish Speech Commands 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 Turkish
-
Turkish Speech Translation
Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.
-
Turkish In-the-Wild Speech
Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.
-
Turkish 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.
-
Turkish Conversational Speech
Speech from natural conversation between two or more people, on open or semi-structured topics, used for conversational AI, voice assistants, and small talk models.
-
Turkish Singing Voice
Vocal recordings with melody, in both a cappella and accompanied form, used for singing voice synthesis, music information retrieval, and lyric alignment.
-
Turkish Read Speech
Recordings of speakers reading specified text, with clear pronunciation and known text, the base material for TTS and ASR.
Speech Commands in other languages
-
Uzbek Speech Commands
Central Asia & Caucasus
-
Hindi Speech Commands
South Asia
-
Arabic (MSA) Speech Commands
Middle East & North Africa
-
Indonesian Speech Commands
Southeast Asia
-
Thai Speech Commands
Southeast Asia
-
Vietnamese Speech Commands
Southeast Asia
Request Turkish Speech Commands
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.