IARPA Babel Kazakh Language Pack IARPA-babel302b-v1.0a
|Item Name:||IARPA Babel Kazakh Language Pack IARPA-babel302b-v1.0a|
|Author(s):||Aric Bills, Thomas Conners, Anne David, Eyal Dubinski, Jonathan G. Fiscus, Mary Harper, Brook Hefright, Kirill Kozlov, Jennifer Melot, Jessica Ray, Anton Rytting, Josh Phillips, Marle Walter, Wade Shen, Ronnie Silber, Evelyne Tzoukermann|
|LDC Catalog No.:||LDC2018S13|
|Release Date:||September 17, 2018|
|DCMI Type(s):||Sound, Text|
|Data Source(s):||telephone conversations|
IARPA Babel Kazakh Agreement (Not-For-Profit)
IARPA Babel Kazakh Agreement (Non-Member)
IARPA Babel Kazakh Agreement (For-Profit)
|Online Documentation:||LDC2018S13 Documents|
|Licensing Instructions:||Subscription & Standard Members, and Non-Members|
|Citation:||Bills, Aric, et al. IARPA Babel Kazakh Language Pack IARPA-babel302b-v1.0a LDC2018S13. Web Download. Philadelphia: Linguistic Data Consortium, 2018.|
|Related Works: Hide||View|
IARPA Babel Kazakh Language Pack IARPA-babel302b-v1.0a was developed by Appen for the IARPA (Intelligence Advanced Research Projects Activity) Babel program. It contains approximately 203 hours of Kazakh conversational and scripted telephone speech collected in 2013 and 2014 along with corresponding transcripts.
The Babel program focuses on underserved languages and seeks to develop speech recognition technology that can be rapidly applied to any human language to support keyword search performance over large amounts of recorded speech.
The Kazakh speech in this release represents that spoken in the Northeastern and Southern dialect regions of Kazakhstan. The gender distribution among speakers is approximately equal; speakers' ages range from 16 years to 64 years. Calls were made using different telephones (e.g., mobile, landline) from a variety of environments including the street, a home or office, a public place, and inside a vehicle.
Audio data is presented as 8kHz 8-bit a-law encoded audio in sphere format and 48kHz 24-bit PCM encoded audio in wav format. Transcripts are encoded in UTF-8. Further information about transcription methodology is contained in the documentation accompanying this release.
None at this time.