What is Dictionary Data?
Structured dictionary entries with definitions, parts of speech, pronunciation, and example sentences, used for dictionary products and lexical understanding tasks.
What buyers get wrong
Rights in dictionary data are tangled, and many existing dictionaries cannot be used commercially as they are. The structured format also has to align with the buyer's system.
The specification detail that decides everything
Output format (JSON / XML / CSV) and whether pronunciation audio is included.
This is the line item that most often separates a dataset that works from one that gets re-ordered. It belongs in the specification before production starts, not in the delivery review.
How we source dictionary data
We do not hold inventory in this category. A requirement comes in, we match it to a producer who can meet the specification, and we agree the quality bar with both sides before recording begins. A pilot batch goes first so misalignments surface early.
Specification at a glance
| Category | Dictionary Data |
|---|---|
| Group | Non-speech data |
| Critical spec | Output format (JSON / XML / CSV) and whether pronunciation audio is included. |
| Included by default | Pilot batch, metadata schema, source and consent documentation |
| Pricing | Quoted from specification — no published rates |
Related categories
-
LLM Training Data
Text corpora for LLM pretraining and fine-tuning — instruction data, preference data, and multi-turn dialogue data.
-
Computer Vision Data
Annotated image and video data, with annotation types including classification, bounding boxes, segmentation masks, and keypoints.
-
NLP Data
Annotated text for NLP tasks — named entities, dependency syntax, sentiment polarity, and relation extraction.
-
Multilingual Language Data
Parallel or non-parallel text corpora spanning multiple languages, used for multilingual models and low-resource language research.
-
Translation Data
Parallel corpora pairing source and target language, used for machine translation training and evaluation.
-
Text Data
General-purpose text corpora from web pages, forums, reviews and similar sources, used for language model pretraining and text classification.
Questions about dictionary data
Do you have dictionary data available now?
No — we do not hold inventory. Everything is produced against a specification. That means the timeline starts when the spec is agreed rather than immediately, and it also means the data matches your requirement instead of approximately matching something already built.
Can this be combined with other categories in one delivery?
Yes, and it is common. A single specification can cover several categories across several languages, with one pilot batch and one quality bar. It usually reduces total cost because speaker recruitment and project setup are shared.
What does the consent documentation cover?
Signed speaker consent stating the intended use, the collection methodology, and the annotation guideline the data was produced under. For projects involving EU data subjects the chain is built to satisfy GDPR, including the transfer mechanism.
Request dictionary data
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.