aidataservices.inAI data collection · India

Dataset specification · Production cohort

1,000 speakers of Kannada Spontaneous Speech

A production cohort build of 1,000 speakers of Kannada spontaneous speech. Generalisation across speakers, which is what actually drives real-world ASR robustness. Speakers talk unscripted on prompted topics — describing a process, recounting an event, arguing a position — with a moderator who prompts but does not lead.

Request a dataset quoteReply within one working day
Structured dataset packages ready for delivery — 1,000 speakers of Kannada Spontaneous Speech
Volume
1,000 speakers
Scale
Production cohort
Per speaker
25–40 minutes of accepted audio per speaker
Accepted yield
60–70% of recorded time is accepted
01

How Kannada 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.

Production cohort — what the build is actually made ofCitiesSix to eightStudiosEight rooms plus two mo…RecruitersEight coordinators, one…Audio yield~500 hours at 30 minute…Sessions per day45–55Team1 programme lead, 1 reg…
02

The specification

FieldValue
LanguageKannada (kn-IN, Kannada)
Volume1,000 speakers
Equivalent500 hours at 30 minutes per speaker
Speech typeSpontaneous Speech
Per speaker25–40 minutes of accepted audio per speaker
File granularitySession-length WAV plus segmented utterance files with offsets into the parent
SegmentationPause-boundary segmentation, reviewed by a native listener rather than left to VAD
Moderator channelRecorded separately and excluded from the delivered speaker audio
Disfluency conventionFilled pauses, repetitions and false starts transcribed, not normalised away
DialectsBangalore urban, Mysuru (standard literary), Dharwad / North Karnataka, Mangaluru coastal
TranscriptionVerbatim, native-speaker, second-pass reviewed
Annotators writing prompts and responses for LLM training data — supporting 1,000 speakers of kannada spontaneous speech
Annotators writing prompts and responses for LLM training data
03

Designing the topic bank for Kannada

  • 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 Kannada specifically: North Karnataka speech has markedly different intonation and lexicon from Mysuru standard
  • Code-mixing handled explicitly rather than edited out — Bengaluru is a migration city: Kannada speech there is mixed with English, Hindi, Tamil and Telugu. Native-only Kannada cohorts recruited in Bengaluru are hard to fill without screening for years of residence.
04

Running a production cohort Kannada build

Nine to twelve weeks, with recruitment running continuously rather than in a front-loaded phase.

Six to eight batches, speaker-disjoint by construction so held-out speakers are genuinely held out.

Screen Bengaluru participants for native fluency and years of Karnataka residence; otherwise the cohort drifts towards second-language Kannada.

ParameterAt this volume
CitiesSix to eight — Bengaluru, Mysuru, Hubballi-Dharwad, Mangaluru, Kalaburagi
StudiosEight rooms plus two mobile rigs
RecruitersEight coordinators, one regional manager
Audio yield~500 hours at 30 minutes per speaker
Sessions per day45–55
Team1 programme lead, 1 regional manager, 8 coordinators, 14 engineers, 25 transcribers, 3 QA leads
05

Cohort design

At 1,000 speakers the quota matrix is enforced per cell, not in aggregate. Every dialect, age and gender combination carries its own target and is signed off individually before final acceptance, because an aggregate 50/50 split can hide a cell that was never filled at all.

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.

DimensionTypical splitWhy it matters for Kannada
Gender50 / 50Pitch range differences change acoustic model behaviour; unbalanced cohorts bias recognition
Age18-25: 30%, 26-40: 40%, 41-60: 30%Older speakers retain conservative Kannada forms that younger urban speakers have lost
RegionKarnataka / parts of Maharashtra, Tamil Nadu and Andhra Pradesh and othersDialect spread across 5 recognised varieties
EducationMixed, including below-graduatePrompt-reading fluency correlates with education and skews prosody
ConditionStudio / quiet room / fieldMatch the noise profile of your deployment
06

Kannada-specific considerations

  • North Karnataka speech has markedly different intonation and lexicon from Mysuru standard
  • Bengaluru is a migration city: Kannada speech there is mixed with English, Hindi, Tamil and Telugu. Native-only Kannada cohorts recruited in Bengaluru are hard to fill without screening for years of residence.
  • Mysuru/Bengaluru standard dominates. North Karnataka (Dharwad, Kalaburagi) and coastal Mangaluru speech are barely represented in any public corpus.
07

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
  • Northern lexical items replaced with standard equivalents
  • Inconsistent transliteration of English technical terms

100% technical QA, 10% content QA stratified by city and coordinator, with voice-based duplicate detection across the whole cohort.

08

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
09

Risks at production cohort in Kannada

Cost at this band is driven by: Number of distinct demographic cells rather than total speakers.

  • Speaker-disjoint splits are only trustworthy if duplicate detection is voice-based rather than ID-based, since one person can present two identities
  • Coordinator-level demographic bias becomes measurable at this size and should be reported, not smoothed over
  • Kannada carries 5 recognised varieties across Karnataka, parts of Maharashtra, Tamil Nadu and Andhra Pradesh, so the quota matrix is wider than the headline volume suggests
  • Mysuru/Bengaluru standard dominates. North Karnataka (Dharwad, Kalaburagi) and coastal Mangaluru speech are barely represented in any public corpus.
10

Deliverables

  • WAV audio to your naming convention, with the per-file manifest
  • Verbatim Kannada 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
11

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 1,000 speakers of Kannada enough?

Enough for production ASR generalisation and for a speaker-verification corpus with meaningful negative pairs.

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 a production cohort Kannada build take?

Nine to twelve weeks, with recruitment running continuously rather than in a front-loaded phase. Six to eight batches, speaker-disjoint by construction so held-out speakers are genuinely held out.

What does 1,000 speakers of Kannada spontaneous speech cost?

Quoted per delivered hour against this specification. At this band the drivers are number of distinct demographic cells rather than total speakers. Send the spec and you get one fixed figure.

How much QA is applied at this volume?

100% technical QA, 10% content QA stratified by city and coordinator, with voice-based duplicate detection across the whole cohort.

Quote this Kannada dataset

1,000 speakers, spontaneous speech, Kannada — production cohort. Adjust anything and send it.

Request a dataset quote