South Asia · Devanagari
Nepali Code-Switching Speech Dataset
Nepali code-switching 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 code-switching speech in Nepali is its own problem
Nepali code-switching is mainly with English, and the density tracks closely with the language a speaker was educated in — people from English-medium schools switch more often. Leave speaker background unannotated and the switching-density distribution in the data has no explanation.
The field to pin down first: Annotate the language of education for each speaker, and deliver stratified by switching density.
At a glance
| Language | Nepali |
|---|---|
| Primary region | South Asia |
| Writing system | Devanagari |
| Category | Code-Switching Speech |
| Specification field to settle first | Annotate the language of education for each speaker, and deliver stratified by switching density. |
| Delivery | Sourced to order, pilot batch before the full run |
What code-switching speech data is
Speech that mixes two or more languages inside a single utterance — Hinglish, Spanglish, Taglish — used for recognition in real spoken settings.
What buyers get wrong about it
The switch point is the hard part — where language A gives way to B inside a sentence, different annotators can place it several words apart. The guideline has to be fixed before annotation starts.
The specification field that decides the quote
Whether annotation marks word-level switch points or only tags the language of the whole utterance — the workload differs by a multiple.
The language side: what Nepali demands
Usable Nepali speech data is surprisingly scarce, and the accent layers of speakers across borders (Nepal, Sikkim in India, Bhutan) are poorly mapped. Speaker metadata — nationality, home region, language of education — has to be recorded item by item.
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 Nepali Code-Switching Speech
How many distinct speakers can you provide for Nepali Code-Switching 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. Annotate the language of education for each speaker, and deliver stratified by switching density.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. Nepali code-switching is mainly with English, and the density tracks closely with the language a speaker was educated in — people from English-medium schools switch more often. 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 Nepali Code-Switching 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 Nepali
-
Nepali Voice Assistant
Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.
-
Nepali Elderly Voice
Speech data from elderly speakers, usually stratified by age band and health status, used for voice products built for older users.
-
Nepali Accented English
English speech from non-native speakers or specific regional accents, grouped by accent origin, used to improve accent robustness in ASR.
-
Nepali Speech Translation
Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.
-
Nepali In-the-Wild Speech
Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.
-
Nepali 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.
Code-Switching Speech in other languages
-
Filipino Code-Switching Speech
Southeast Asia
-
Persian Code-Switching Speech
Middle East & North Africa
-
Tamil Code-Switching Speech
South Asia
-
Telugu Code-Switching Speech
South Asia
-
Malayalam Code-Switching Speech
South Asia
-
Sinhala Code-Switching Speech
South Asia
Request Nepali Code-Switching 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.