Concepts / Synthetic Data for Language Models

Synthetic Data for Language Models

Demonstration data needs labelers who can reason, gather information, and judge requests, because the written response is what the model learns to imitate.

  • Programming

Teachers Who Write the Answers

Think about what makes a good classroom teacher. A student learns less from a teacher who explains things carelessly or answers questions with errors, and more from one who models clear, careful, thoughtful reasoning. Training a conversational AI works in a similar way. The people who write example conversations for the model act as its teachers, so the quality of those examples shapes how well the model learns to hold an intelligent conversation.

This article focuses on one stage of the training pipeline: the stage where people write demonstration data for a model that has already been pre-trained. You will see what makes this work hard, what it costs, who tends to do it, and what alternatives teams have explored when high-quality human writing is too expensive or slow to scale.

What do you think happens?

When a model learns from a hand-written example response, what does it actually pick up?

  • Only the facts mentioned in the response

  • Only the wording of the sentences

  • The response itself, including how carefully or shallowly it was produced

Reveal answer
Answer:

The model learns to imitate the written response, including how carefully it was reasoned.

The written response is what the model learns to imitate. A careless or shallow response does not just produce one bad data point; it teaches the model that shallow responses are acceptable.

What a Labeler Actually Does

Many traditional data labeling jobs can be done with little or no specialized knowledge. Deciding whether a photo contains a bicycle is a task most people can perform after a short explanation. Demonstration data is different. A single prompt may require the labeler to reason through a problem, gather relevant information, and decide whether the user's request is appropriate to fulfill at all.

Prompt arrivesReason through theproblemGather relevantinformationJudge whether tofulfill the requestWrite the workedresponseModel imitates theresponse
The steps a labeler may need to work through between receiving a prompt and writing the response that the model will later imitate.

Because each response is a worked piece of reasoning rather than a single tag, the labeler's skill becomes part of the training signal. The pipeline above is why demonstration data cannot be produced by just anyone: every step is a place where a weaker writer can leave a mark that the model will later reproduce.

Tracing One Careless Response Through Training

The easiest way to see the stakes is to follow a single prompt through two different writing processes. The prompt is the same in both cases; only the response differs, and the model cannot tell the difference between them. It only sees a pair to imitate.

Worked example

One prompt, two responses

A labeler receives a prompt that requires reasoning and a judgment about whether to answer. Trace what the model is shown and what it learns in two cases.

  1. 1
    Careful writing process

    The labeler reasons through the problem, gathers the relevant information, judges whether the request should be fulfilled, and writes a worked response that shows that thinking.

  2. 2
    What the model sees in the careful case

    The pair contains a response that models clear reasoning, so the model is imitating careful, thoughtful behavior.

  3. 3
    Careless writing process

    The labeler skips the reasoning and gathering steps and writes a shallow answer, which may contain errors.

  4. 4
    What the model learns in the careless case

    The pair is still a training example. It teaches the model that shallow responses are acceptable, not just that this one answer is weak.

Result

A single weak pair does more than add one bad data point. It reinforces a pattern the model can imitate across many conversations.

Why Hand-Written Pairs Are Expensive

The before-and-after comparison in the source shows why this work is expensive. A task that takes seconds per item can be spread across huge numbers of cheap annotations. Writing a demonstration pair can take up to 30 minutes, so it must be budgeted very differently. A dataset of thousands of pairs quickly becomes a major expense.

To estimate scale, multiply the number of pairs by the time per pair to get labeling hours, and multiply the number of pairs by the direct cost per pair to get the direct cost. The table below applies those two multiplications to 30 minutes per pair and 10 dollars per pair, using the figures named in the source. Each row is a worked calculation for a different dataset size.

Number of hand-written pairsMaximum labeling hours at 30 minutes eachDirect cost at 10 dollars each
1,00050010,000 dollars
10,0005,000100,000 dollars
13,0006,500130,000 dollars

Direct costs only. The 13,000-pair row matches the scale named in the source.

Whose Perspective Ends Up in the Model

Because the work demands judgment and domain sense, companies tend to rely on highly educated labelers. The profile of the labeler pool matters for two reasons. It affects the quality of the writing, and it affects whose perspective ends up embedded in the model.

Labeler backgroundExperience and perspectiveWritten responsesDemonstration dataModel behaviorshapesformsis imitated
A labeler's background shapes the written responses, which become demonstration data, which the model imitates.

Labeler demographics matter because a skewed pool can carry bias into the model. The source gives one concrete case: a volunteer survey in which 90 percent of respondents identified as male. A pool like that can shape which perspectives the written examples reflect, and the model learns to imitate those perspectives along with the wording.

Four Sources of Demonstration Data

Since expert writing is slow and costly, not every organization can follow the high-quality human annotation route. Several alternatives have appeared, and each trades something away. Human expert writing, volunteer crowds, heuristic filtering of internet dialogues, and AI-generated data can all be compared on who produces the data, what it costs, and how reliable it is.

SourceWho or what produces itWhat it gainsWhat it gives up
Human expert writingHighly educated labelers writing worked responsesCareful reasoning and judgment in each responseSlow and costly, up to 30 minutes per pair
Volunteer crowdsVolunteers worldwide, mobilized by LAION, a non-profitScale: 10,000 conversations, 161,443 messages in 35 languages, and 461,292 quality ratingsThe volunteer pool was not carefully controlled for bias
Heuristic filteringSimple heuristics that filter internet text for dialogues, as DeepMind didCheap to run at scale; looks for texts in an alternating speaker formatCan only check the form of a conversation, not whether its reasoning or judgment is strong
AI-generated dataModel-produced examples, used by many teams to reduce dependence on human annotated dataReduces dependence on high-quality human annotated dataThe source names this as the newest approach and points to synthetic data elsewhere in the course for more detail

The four demonstration data sources named in the source, compared on producer, gain, and limitation.

Human expert writingHighly educated labelersVolunteer crowds13,500 volunteersHeuristic filteringAlternating speaker formatAI-generated dataModel-produced examples
Each approach reduces dependence on expert writing in a different way and comes with its own limitation.

The volunteer example shows the trade-off clearly. LAION mobilized 13,500 volunteers worldwide, and together they produced a large body of conversations and ratings. The scale is impressive, but the pool was not carefully controlled for bias, so scale alone does not settle the question of whose perspective the data carries.

The heuristic example shows a different trade-off. DeepMind did not write new conversations. Its team filtered internet text for dialogues arranged in an alternating speaker format. A filter like this is cheap to run at scale, but it can only check the form of a conversation. It cannot confirm that the reasoning or judgment inside the conversation is strong.

Why Pre-Training Still Comes First

Mistakes That Undermine Demonstration Data

  • Common mistake

    Assuming any labeler can write demonstration data

    What it looks like

    Deciding whether a photo contains a bicycle is a task most people can perform after a short explanation.

    Why it fails

    Demonstration data can require reasoning through a problem, gathering information, and judging whether the request should be fulfilled at all.

    Do this instead

    Recognize that the writing demands judgment and domain sense, which is why companies tend to rely on highly educated labelers.

  • Common mistake

    Treating a cheap filter as a quality check on reasoning

    What it looks like

    A heuristic filter finds dialogues in an alternating speaker format.

    Why it fails

    Such a filter can only check the form of a conversation, not whether its reasoning or judgment is strong.

    Do this instead

    Use cheap filters for form, and do not read a passed filter as evidence that the content is high quality.

  • Common mistake

    Counting only the time spent writing each pair

    What it looks like

    A team budgets 30 minutes per pair and stops there.

    Why it fails

    Direct costs add up quickly before design and quality control are counted.

    Do this instead

    Budget for design and quality control alongside the writing time.

  • Common mistake

    Ignoring who the labelers are because the responses read well

    Why it fails

    A skewed labeler pool can carry bias into the model, and the perspective embedded in the writing is not visible in the text alone.

    Do this instead

    Examine labeler demographics as part of judging demonstration data quality.

Estimating a Hand-Written Dataset

EASY

A team plans to write 5,000 demonstration pairs by hand. Each pair takes at most 30 minutes, and the direct cost is 10 dollars per pair. What is the maximum total labeling time in hours, and what is the direct cost? Note whether your answer includes design and quality control.

Hints
  • Multiply 5,000 pairs by 30 minutes to get total minutes, then divide by 60 to convert to hours.
  • Multiply 5,000 pairs by 10 dollars to get the direct cost.
  • The answer is 2,500 hours and 50,000 dollars. Both figures are direct costs only and exclude design and quality control.

Key Takeaways

  1. 1
    Demonstration data needs labelers who can reason, gather information, and judge requests, because the written response is what the model learns to imitate.
  2. 2
    Careless responses teach the model that shallow responses are acceptable, so each pair carries the labeler's skill into training.
  3. 3
    Hand-written pairs are expensive: up to 30 minutes each, and direct costs grow quickly before design and quality control are counted.
  4. 4
    Labeler demographics can carry bias into the model, as the volunteer survey with 90 percent male respondents illustrates.
  5. 5
    Volunteer crowds, heuristic filtering, and AI-generated data each reduce dependence on expert writing but come with their own limitations, and pre-training still comes first.

At a glance

  • Demonstration data needs labelers who can reason, gather information, and judge requests, because the written response is what the model learns to imitate.
  • Careless responses teach the model that shallow responses are acceptable, so labeler skill becomes part of the training signal.
  • Hand-written pairs are expensive: up to 30 minutes each, with direct costs that add up quickly before design and quality control.
  • Labeler demographics can carry bias into the model, and a skewed pool shapes whose perspective is embedded in the data.
  • Volunteer crowds, heuristic filtering, and AI-generated data reduce dependence on expert writing, each with its own limitation.

Related concepts

More concepts starting with S