Dataset specification · Evaluation scale
100 hours of Bengali Spontaneous Speech
An evaluation scale build of 100 hours of Bengali spontaneous speech. Building a benchmark or evaluation set that is large enough to trust, or fine-tuning a narrow domain. 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
- 100 hours
- Scale
- Evaluation scale
- Per speaker
- 25–40 minutes of accepted audio per speaker
- Accepted yield
- 60–70% of recorded time is accepted
How Bengali 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 | Bengali (bn-IN, Bengali) |
| Volume | 100 hours |
| Equivalent | 200 speakers at 30 minutes each, or 100 speakers at one hour each |
| 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 | Kolkata standard (Rarhi), Sylheti-influenced, Rangpuri / North Bengal, Medinipuri |
| Transcription | Verbatim, native-speaker, second-pass reviewed |

Designing the topic bank for Bengali
- 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 Bengali specifically: Inherent vowel is realised as /ɔ/ or /o/, which breaks G2P rules copied from Devanagari-based systems
- Code-mixing handled explicitly rather than edited out — Kolkata professional speech mixes English heavily; rural West Bengal much less. A single 'Bengali' dataset without register tags conflates two very different acoustic and lexical distributions.
Running an evaluation scale Bengali build
Four to six weeks. Two cities running in parallel means recruitment and recording overlap rather than queue behind each other.
Three batches at roughly two-week intervals, each one a self-contained, speaker-disjoint slice you can evaluate independently.
Tag every speaker as Indian Bengali and record district of origin; mixing in Bangladeshi speech without tags is a common and costly dataset defect.
| Parameter | At this volume |
|---|---|
| Cities | Two, chosen for dialect contrast — Kolkata, Siliguri |
| Studios | Two rooms running in parallel |
| Recruiters | Two coordinators |
| Speakers | ~200–240 |
| Sessions per day | 12–16 across both cities |
| Team | 2 coordinators, 4 engineers, 6 transcribers, 1 QA lead |
Cohort design
At 100 hours the cohort is deliberately simplified: two or three dialect groups rather than the full spread, with quotas enforced in aggregate. A build this size cannot support per-cell targets and should not claim to.
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 Bengali |
|---|---|---|
| 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 Bengali forms that younger urban speakers have lost |
| Region | West Bengal / Tripura / Assam (Barak Valley) and others | Dialect spread across 5 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 |
Bengali-specific considerations
- Inherent vowel is realised as /ɔ/ or /o/, which breaks G2P rules copied from Devanagari-based systems
- Kolkata professional speech mixes English heavily; rural West Bengal much less. A single 'Bengali' dataset without register tags conflates two very different acoustic and lexical distributions.
- Indian Bengali is under-collected relative to Bangladeshi Bengali, and North Bengal and Tripura varieties are almost entirely missing.
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
- Three sibilant characters chosen inconsistently for the same sound
- Bangladeshi vs Indian Bengali orthographic conventions mixed within one dataset
100% technical QA, 25% content QA, escalating to full review on any batch that fails the agreed error threshold.
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 scale in Bengali
Cost at this band is driven by: Dialect spread is the main driver at this band — two contrasting cities cost more than two convenient ones; Turnaround compression, if you need it inside four weeks.
- Two-city cohorts can hide a dialect gap that only appears when the model meets a third region
- Transcription consistency between two city teams needs an explicit convention document or the batches will not match
- Bengali carries 5 recognised varieties across West Bengal, Tripura, Assam (Barak Valley), so the quota matrix is wider than the headline volume suggests
- Indian Bengali is under-collected relative to Bangladeshi Bengali, and North Bengal and Tripura varieties are almost entirely missing.
Deliverables
- WAV audio to your naming convention, with the per-file manifest
- Verbatim Bengali 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 100 hours of Bengali enough?
A solid evaluation set, and enough to fine-tune an existing multilingual model on a narrow domain. Still short of what a general production model needs.
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 scale Bengali build take?
Four to six weeks. Two cities running in parallel means recruitment and recording overlap rather than queue behind each other. Three batches at roughly two-week intervals, each one a self-contained, speaker-disjoint slice you can evaluate independently.
What does 100 hours of Bengali spontaneous speech cost?
Quoted per delivered hour against this specification. At this band the drivers are dialect spread is the main driver at this band — two contrasting cities cost more than two convenient ones and turnaround compression, if you need it inside four weeks. Send the spec and you get one fixed figure.
How much QA is applied at this volume?
100% technical QA, 25% content QA, escalating to full review on any batch that fails the agreed error threshold.
Quote this Bengali dataset
100 hours, spontaneous speech, Bengali — evaluation scale. Adjust anything and send it.