Instruction tuning data
Prompts and model-quality answers written by people who know the domain, for supervised fine-tuning by your team.
For assistants that follow instructions
LLM training data is the prompts, answers and human judgments that teach a large language model how to behave. We put it together with people from our 30,000+ network, in the 50 most widely spoken languages and deep across Indian ones. Your team does the training.
prompt · written by a person
user Explain a bank overdraft to someone opening their first account.
prompttwo answers · which is better?
checked before delivery
follows guideline second review English and Hindi reason written
reviewedLLM training data is the text a large language model learns from and gets checked against: prompts paired with good answers, comparisons that say which answer people prefer, multi-turn conversations and held-back test sets. For a model that has to follow instructions and sound right to real users, most of that data is written or judged by people.
Pretraining uses huge amounts of general text. The data that shapes how a model behaves afterwards is much smaller, and much more deliberate. Someone has to write the good answer, or read two answers and say which one is better, and do it the same way a few thousand times.
We don't train or fine-tune your model. We put the data together with people from our network and check it, and your team does the training.
Prompt, answer and preference labels need the same discipline as any annotation task, and the guide to annotation quality covers what that discipline looks like.
The same kind of prompt, shown as four kinds of LLM data. Tap through them. It's a made-up example, and your guideline decides what the real thing looks like.
A prompt and one good answer, written by a person who knows the subject. The model learns what a helpful reply looks like by seeing thousands of them.
People read two or more answers to the same prompt and pick the better one, with a short reason. Your team uses these judgments for RLHF or a similar method.
People rate your model's answers against the targets you set, and results get split by language and topic so weak spots show. See data and model evaluation.
Prompts and answers written by native speakers, not run through translation and left there. It covers the 50 most widely spoken languages, and goes deep on Indian ones.
Six kinds of data, all written or judged by people and reviewed before delivery. Most projects mix two or three.
Prompts and model-quality answers written by people who know the domain, for supervised fine-tuning by your team.
For assistants that follow instructions
Two or more answers compared or put in order by people, with a reason, for RLHF and similar methods your team runs.
For answers that match what users prefer
Multi-turn dialogues written or role-played by people, so a model learns to follow a thread. More on conversational AI data.
For chat assistants and support bots
Test prompts and human ratings of your model's answers, split so weak spots show. See data and model evaluation.
For checking a model before and after launch
Prompts and answers written by native speakers across the 50 most widely spoken languages. See translation and localization.
For models used outside English
Hindi, Tamil and many more, including the mixed Hindi and English people actually type. See Indian language data.
For assistants for users in India
A few of the jobs LLM data ends up doing. These are typical projects, not a client list. For raw text, the text data page covers collection and labeling.
Prompt and answer pairs that show a model what a helpful reply looks like.
Human preferences your team feeds into RLHF or a similar method.
Multi-turn conversations in the tone your customers expect.
Rated answers across topics and languages, before and after launch.
Native-written data in the languages your users speak.
Hindi, Tamil and mixed-script data from native speakers.
Every LLM data project we've seen goes smoother when these are written down on day one, because they're what the writers and raters will argue about later.
Tone, length, format and when the model should decline. Put examples of good and bad answers in the guideline.
A simple pick, a full ranking or a score, and whether raters write a reason.
Which subjects the data has to cover, and how much expertise the writers need for each.
Which languages, whether answers are written natively or translated and checked, and how mixed-language messages are handled.
One named person owns the project. Each step below links to the service behind it.
The kind of data, topics, languages and rough volume.
Signed before any prompt or data moves.
Written with you, with good and bad examples.
People from our network write prompts and answers.
Answers compared, put in order or rated, then reviewed.
Held-back prompts check your model after training.
We cover the 50 most widely spoken languages in the world and go deep on Indian ones, well past Hindi and English. Answers are written by native speakers, not left as machine translation.
The words that come up on an LLM data project. The full AI training data glossary has the rest.
The same team does all of these. You can also compare all eight services.
People who write prompts and answers.
Answers compared, rated and reviewed.
Your LLM's answers checked against targets.
Multi-turn dialogue for chat assistants.
Native checks in every language.
What people ask us about LLM data. The services FAQ covers how the services fit together.
The text a large language model learns from and gets checked against: prompts paired with good answers, comparisons that say which answer is better, multi-turn conversations, and test sets. For a model that has to follow instructions, most of the useful data is written or judged by people.
RLHF stands for reinforcement learning from human feedback. The data behind it is usually preference data: people read two or more answers to the same prompt and pick or rank the better one, often with a short reason. Your team then uses those judgments to train a reward model and tune the LLM.
Instruction tuning data shows the model a prompt and one good answer to copy. Preference data shows it several answers and says which one people liked more. Teams often start with the first and add the second.
No. We provide the data, and your team trains or fine-tunes your own model with it. We can also check your model's answers afterwards, as part of our evaluation work.
The 50 most widely spoken languages in the world, with deep coverage of Indian languages, well past Hindi and English. Our Indian language data page has more on that side.
Everyone works from the same written guideline, a second person reviews a share of each batch, and disagreements go back into the guideline as worked examples. That's the same loop we use for any labeling work.
Yes. Send a short brief and we'll put together a small sample free before you commit.
Yes. The NDA is signed before any data moves, we use your prompts and data only for the scope we agreed, and only the people on your project can see them. It's returned or deleted when you ask.
Pick the kinds of LLM data, add the languages and a rough volume, and send it. We'll put together a small sample free before you commit.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.