Dataset specification · Evaluation cohort
500 speakers of Hindi Spontaneous Speech
An evaluation cohort build of 500 speakers of Hindi spontaneous speech. Speaker-count-driven work: verification, diarisation and accent robustness, where breadth matters more than hours. Speakers talk unscripted on prompted topics — describing a process, recounting an event, arguing a position — with a moderator who prompts but does not lead.

- Volume
- 500 speakers
- Scale
- Evaluation cohort
- Per speaker
- 25–40 minutes of accepted audio per speaker
- Accepted yield
- 60–70% of recorded time is accepted
How Hindi spontaneous speech is captured
Speakers talk unscripted on prompted topics — describing a process, recounting an event, arguing a position — with a moderator who prompts but does not lead.
A 60-minute session covering six to eight topics, recorded continuously and segmented afterwards into utterances at natural pause boundaries.
Yield at this style: 60–70% of recorded time is accepted. Long silences, moderator speech and abandoned topics are cut in post, so recorded hours run well ahead of delivered hours. Budget for the gap.
The specification
| Field | Value |
|---|---|
| Language | Hindi (hi-IN, Devanagari) |
| Volume | 500 speakers |
| Equivalent | 250 hours at 30 minutes per speaker |
| Speech type | Spontaneous Speech |
| Per speaker | 25–40 minutes of accepted audio per speaker |
| File granularity | Session-length WAV plus segmented utterance files with offsets into the parent |
| Segmentation | Pause-boundary segmentation, reviewed by a native listener rather than left to VAD |
| Moderator channel | Recorded separately and excluded from the delivered speaker audio |
| Disfluency convention | Filled pauses, repetitions and false starts transcribed, not normalised away |
| Dialects | Khari Boli, Awadhi, Braj, Bhojpuri-influenced Hindi |
| Transcription | Verbatim, native-speaker, second-pass reviewed |

Designing the topic bank for Hindi
- Topic banks graded by familiarity, so speakers across education and occupation bands all have something to say
- Open prompts only — anything answerable with yes or no produces thirty seconds of audio and a stalled session
- Culturally grounded topics per region, since a prompt that works in Mumbai can draw blank looks in Guwahati
- Topic rotation across the cohort so the corpus does not over-represent a handful of subjects
- Built against Hindi specifically: Four-way stop contrast (voiced/voiceless x aspirated/unaspirated) that collapses in models trained on English-first acoustic units
- Code-mixing handled explicitly rather than edited out — Urban Hindi speech is Hinglish in practice. Expect 15-40% English tokens in spontaneous speech: numbers, brands, technology terms, and whole clause switches. Any Hindi corpus that excludes English tokens will not match production traffic.
Running an evaluation cohort Hindi build
Six to eight weeks. Speaker-count targets front-load recruitment, so the coordinator team is proportionally larger than an equivalent hours-based build.
Four batches, each one a demographically complete slice rather than a convenient chunk, so early batches are usable for training on their own.
Largest recruitment pool in the network. A 1,000-speaker Hindi cohort with balanced gender and 18-45 age bands is typically fielded across four cities to avoid a single-city accent bias.
| Parameter | At this volume |
|---|---|
| Cities | Three to four — Delhi, Lucknow, Jaipur, Patna, Bhopal |
| Studios | Four rooms |
| Recruiters | Four coordinators |
| Audio yield | ~250 hours at 30 minutes per speaker |
| Sessions per day | 25–30 |
| Team | 1 programme lead, 4 coordinators, 8 engineers, 14 transcribers, 2 QA leads |
Cohort design
At 500 speakers quotas are enforced per dialect and reconciled fortnightly. Aggregate demographics are reported per batch so drift is visible while there is still time to correct it.
Screening is for willingness to talk, not literacy, which opens the cohort to speakers a scripted protocol would exclude. Expect to over-recruit by 15% for speakers who freeze on the day.
| Dimension | Typical split | Why it matters for Hindi |
|---|---|---|
| Gender | 50 / 50 | Pitch range differences change acoustic model behaviour; unbalanced cohorts bias recognition |
| Age | 18-25: 30%, 26-40: 40%, 41-60: 30% | Older speakers retain conservative Hindi forms that younger urban speakers have lost |
| Region | Uttar Pradesh / Bihar / Madhya Pradesh and others | Dialect spread across 7 recognised varieties |
| Education | Mixed, including below-graduate | Prompt-reading fluency correlates with education and skews prosody |
| Condition | Studio / quiet room / field | Match the noise profile of your deployment |
Hindi-specific considerations
- Four-way stop contrast (voiced/voiceless x aspirated/unaspirated) that collapses in models trained on English-first acoustic units
- Urban Hindi speech is Hinglish in practice. Expect 15-40% English tokens in spontaneous speech: numbers, brands, technology terms, and whole clause switches. Any Hindi corpus that excludes English tokens will not match production traffic.
- Public Hindi corpora skew heavily towards read newspaper text from educated urban speakers in Delhi and NCR. Rural Bihar and eastern UP speech, elderly speakers, and low-literacy speakers reading prompts aloud are largely absent.
Quality gates for spontaneous speech
- Segment boundary review — bad boundaries produce truncated words that poison training more than they help
- Disfluency transcription consistency audited across transcribers, since conventions drift fast on this style
- Moderator speech confirmed absent from delivered segments
- Topic distribution checked per speaker so one dominant subject does not skew the language model
- Inconsistent Devanagari vs romanised spelling for the same English loan word
- Nukta characters (क़ ख़ ग़ ज़ फ़) applied inconsistently by transcribers
100% technical QA, 15% content QA, plus mandatory duplicate-speaker detection across cities.
What goes wrong on spontaneous speech sessions
- Speakers who dry up after a minute, leaving sessions that look complete by duration but are mostly silence
- Drift into a reading register when a speaker becomes self-conscious about the microphone
- Moderator over-prompting, which turns a monologue corpus into an interview corpus
- Transcriber normalisation — quietly cleaning up disfluencies destroys the exact signal this style exists to capture
Risks at evaluation cohort in Hindi
Cost at this band is driven by: Cohort breadth and screening depth, not recorded hours.
- Duplicate speakers across cities inflate the apparent cohort and quietly corrupt speaker-disjoint splits
- Recruiting for breadth tempts coordinators toward the easiest available demographic, which needs weekly quota audit
- Hindi carries 7 recognised varieties across Uttar Pradesh, Bihar, Madhya Pradesh, so the quota matrix is wider than the headline volume suggests
- Public Hindi corpora skew heavily towards read newspaper text from educated urban speakers in Delhi and NCR. Rural Bihar and eastern UP speech, elderly speakers, and low-literacy speakers reading prompts aloud are largely absent.
Deliverables
- WAV audio to your naming convention, with the per-file manifest
- Verbatim Devanagari transcripts with utterance-level timestamps
- Filled-pause and false-start markers
- Segment offsets into the parent session file
- Topic label per segment
- Speech-rate and pause-density statistics per speaker
- Per-speaker metadata: age band, gender, region, dialect, education band
- Consent records mapped to speaker IDs
- QA report with pass rates, rejection reasons and agreement statistics
- Speaker-disjoint train / dev / test splits on request
What this trains, and what it does not
- Robust ASR for real user speech
- Language modelling on natural syntax
- Disfluency detection and removal
- Prosody and speech-rate modelling
Phonetic balance cannot be guaranteed — speakers say what they say. If you need specific phone contexts or a controlled lexicon, this style has to be paired with a scripted layer.
Frequently asked
Is 500 speakers of Hindi enough?
Enough for reliable per-dialect evaluation and for training speaker-verification and diarisation systems.
Why spontaneous speech rather than another speech type?
Robust ASR for real user speech, Language modelling on natural syntax, Disfluency detection and removal are what this style is the right input for. Phonetic balance cannot be guaranteed — speakers say what they say. If you need specific phone contexts or a controlled lexicon, this style has to be paired with a scripted layer.
How long does an evaluation cohort Hindi build take?
Six to eight weeks. Speaker-count targets front-load recruitment, so the coordinator team is proportionally larger than an equivalent hours-based build. Four batches, each one a demographically complete slice rather than a convenient chunk, so early batches are usable for training on their own.
What does 500 speakers of Hindi spontaneous speech cost?
Quoted per delivered hour against this specification. At this band the drivers are cohort breadth and screening depth, not recorded hours. Send the spec and you get one fixed figure.
How much QA is applied at this volume?
100% technical QA, 15% content QA, plus mandatory duplicate-speaker detection across cities.
Quote this Hindi dataset
500 speakers, spontaneous speech, Hindi — evaluation cohort. Adjust anything and send it.