CertNote/ Commute Study Notes
Roadmap
KOEN
CLF-C02 · FoundationalCloud Practitioner - Foundational
DVA-C02 · AssociateDeveloper - Associate
SAA-C03 · AssociateSolutions Architect - Associate
SOA-C02 · AssociateCloudOps Engineer - Associate
SAP-C02 · ProfessionalSolutions Architect - Professional
DOP-C02 · ProfessionalDevOps Engineer - Professional
Linux Master 2 · 2급KAIT Linux Master - Level 2
SCS-C03 · SpecialtySecurity - Specialty
Linux Master 1 · 1급KAIT Linux Master - Level 1
MLA-C01 · AssociateMachine Learning Engineer - Associate
AIF-C01 · FoundationalAI Practitioner - Foundational
  • Week 1
    • 1.The Relationship and Differences Between AI, Machine Learning, and Deep Learning
    • 2.Learning Types: Supervised, Unsupervised, and Reinforcement Learning
    • 3.Problems Where ML Fits vs. Problems Where It Doesn't
    • 4.Key Terms: Model, Training, Inference, Feature, Label, Overfitting
    • 5.Week 1 Review: AI/ML Fundamentals
  • Week 2
    • 1.ML Lifecycle Overview: One Full Cycle from Data to Operations
    • 2.Data: Structured vs Unstructured, Splitting Data, and the Power of Quality
    • 3.Model Evaluation Basics: Accuracy, Precision, Recall, and Overfitting/Underfitting
    • 4.The Human Role in ML Development: Labeling, Feedback, and Iterative Improvement
    • 5.Week 2 Wrap-Up: ML Lifecycle and Data at a Glance
  • Week 3
  • Week 4
  • Week 5
  • Week 6
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
SQLD · 개발자SQL Developer (SQLD)

© CertNote · 주간랩스

  • About
  • Changelog
  • Contact
  • Terms
  • Privacy
← AIF-C01/Week 2/Day 4

Based on the AIF-C01 exam guide·Report an error

AIF-C01· AssociateWeek 2 · Day 4~31 min read

Day 4 - The Human Role in ML Development: Labeling, Feedback, and Iterative Improvement

📌 Key Takeaways

  • ML is collaboration between people and machines. The impression that "the machine does everything by itself" is nearly the opposite of reality.
  • Labeling: People attach correct answers to data. It is the foundation of supervised learning, and if the labels are wrong, the model learns wrongly too.
  • Feedback: People evaluate and correct the model's answers. In generative AI, RLHF is the representative technique.
  • Human-in-the-loop (HITL): The more important or risky a decision, the more a person does the final review and approval. It is a core safeguard of responsible AI.
  • ML is not "completed" but "continuously improved." Take people out and the model grows stale through drift.

Why People Are Needed

  • AIF-C01 asks about this topic in the context of the "Human-in-the-loop" (a loop in which people intervene) concept and responsible AI.
  • Who tells the model "this photo is a cat"? The machine doesn't know it from the start; people have to tell it.
  • Ultimately judging whether the model's answers are right or wrong, and what is inappropriate, is also done by people.

Of the three learning types from Week 1 (supervised, unsupervised, reinforcement), the one that directly depends on human labeling is supervised learning. Supervised learning learns from "input + correct answer (label)" pairs, while unsupervised learning learns from the structure of the data alone, without answers. At exam entry level, remembering "with labels → supervised, without labels → unsupervised" is enough.

1. Data Labeling — Attaching Correct Answers

  • The work of attaching a "this is what" answer key (label) to raw data.
  • A supervised learning model learns patterns by looking at these labels.
Data typeLabeling examples
ImageMarking "this photo is a cat/dog," drawing boxes around objects in a photo
TextMarking "this review is positive/negative," tagging people's names within sentences
AudioListening to a recording and transcribing it into text
  • Labeling is slow, expensive, and labor-intensive (think of attaching labels one by one to tens of thousands of photos).
  • That is why labeling quality control is a major challenge in ML projects.

⚠️ Pitfall: If the labels are wrong, the model learns wrongly too. If a labeler mistakenly tags a photo of a dog as "cat," the model learns that wrong answer as it is. That is why quality is managed by having several people label the same data and checking their agreement, or by adding a review step.

AWS has a labeling tool called Amazon SageMaker Ground Truth. It manages human labelers and provides features that lighten the people's workload through automatic labeling. For the exam, it is enough to know that "there is an AWS service that helps with labeling."

2. Feedback — Evaluating and Correcting the Model's Answers

  • When the model produces an answer, people evaluate and correct it. This feedback is the key fuel for improving the model.
  • Human feedback is especially decisive in generative AI.
  • Feedback doesn't end after one round: the loop of the model answers → people evaluate → the model improves → it answers again keeps turning.

The representative technique for refining generative AI (large language models) is RLHF (Reinforcement Learning from Human Feedback). When people evaluate which of the model's several answers is better, the model is adjusted toward "the direction people prefer" based on that evaluation. This human feedback is the key to making a chatbot answer in a more helpful and less risky way.

3. Human-in-the-loop — A Person Is Inside the Loop

  • HITL is a design that deliberately inserts human judgment into the operation of an ML system.
  • When the model is unsure, the decision is important, or the risk is high → don't decide automatically; hand it to a person.
SituationWhat HITL does
A judgment the model is unsure aboutRequest review by a person
A high-risk decision (loan denial, medical)A person gives the final approval
The model gave a wrong answerA person corrects it → it is reflected in the next training
Inappropriate or dangerous outputA person filters it out

HITL is a core safeguard of Responsible AI. If you let AI decide everything automatically, there is no way to catch biased judgments or dangerous mistakes. Keeping a person in the loop compensates for the model's limitations and also makes it clear who is accountable for a wrong decision. The principle is "the more important or risky the decision, the stronger the human involvement."

🎯 Scenario: "An AI automatically reviews loan applications, and a denial decision has a major impact on people's lives. How should it be designed?" → Because it is a high-risk decision, apply Human-in-the-loop so that, at minimum, significant decisions such as denials are given a final review and approval by a person.

4. Iterative Improvement — ML Is Not Completed in One Go

  • A large part of the force that turns the cyclical lifecycle from Day 1 is iterative improvement by people.
  • After deployment, people look at real usage results → collect the wrong cases → attach labels to new data → retrain.

An improvement loop that goes from labeling through training, model responses, and human evaluation, then back to training

  • The key point: ML is not "completed" but "continuously improved." Human labels, feedback, and review keep this loop alive.

⚠️ Pitfall: The thought that "once you build a good model, it needs no more human effort" is dangerous. Data changes (drift), new situations appear, and the model grows stale. Without continuous human monitoring and feedback, even a good model collapses over time.

Labeling, Feedback, and Review Happen at Different Points in Time

All three share the fact that "people step in," but they differ in when and on what they step in. The exam mixes up these timings when asking.

CategoryWhenWhat people doOutput
Data labelingBefore trainingAttach correct answers to raw dataLabeled training data
Feedback (RLHF, etc.)While refining the modelEvaluate the model's answers and rank themA model that reflects human preferences
Human evaluationEvaluation before deploymentPeople directly score the quality of the model's outputGrounds for deciding whether to deploy
HITL reviewInference time during operationCheck, approve, or correct individual predictions the model producedA reviewed final decision + corrected cases
Human auditPeriodically during operationDraw a sample and check for bias and errorsProblems found → a trigger for retraining
  • If the passage says "prepare the training data," it is labeling; if it says "pick the better of the model's responses," it is feedback; if it says "a staff member checks the prediction before it goes out to the user," it is HITL review.
  • The responsible AI domain lists label quality analysis, human audits, and subgroup analysis (measuring performance separately for each group) as means of finding bias. All three involve human judgment.

How Does SageMaker Ground Truth Lighten the Human Workload?

Amazon SageMaker Ground Truth is a service that builds labeled datasets using "people + machine learning." There are three things to know.

1) Who does the labeling — three kinds of workforce

WorkforceWho they areSuitable situation
Amazon Mechanical TurkPublic workers around the worldLarge volumes of non-sensitive data, quickly
Private workforceOur company's employees and contractorsData that must not be exposed externally, work requiring in-house expertise
VendorSpecialist labeling companies on AWS MarketplaceWhen handing the whole job to a professional workforce
  • Clue for telling them apart: when the data is sensitive, such as "patient records" or "confidential internal documents," choose a private workforce.

2) Automatic labeling — only the uncertain items go to people

① People label a portion of the sample
        ↓
② Train a labeling model with those results
        ↓
③ The model assigns labels and confidence scores to the remaining data
        ├─ Confidence at or above the threshold → label is confirmed automatically
        └─ Confidence is low                    → send to a person
        ↓
④ Improve the model with the labels people attached, and repeat from ②
  • This approach is called active learning. Machines handle the easy items and people handle the confusing ones, reducing labeling time and cost.
  • People are not removed entirely. The starting sample and the difficult cases remain people's job to the end.

3) Combining several people's answers into one — annotation consolidation

  • Give the same data to two or more people and combine their answers to settle on a single label. This prevents one person's mistake or subjectivity from becoming the correct answer as is.

  • Adding more workers raises label accuracy but also raises cost. It is a trade-off between quality and cost.

  • Note: AWS documentation currently states that Ground Truth is not open to new customers and that only existing customers can continue to use it. For the exam, remember it by its role: "the service that helps with labeling = Ground Truth."

In What Order Does RLHF Proceed?

We'll grasp only the flow, without equations.

StepWhat is doneRole of people
①Collect questions and model answersPeople write good answers themselves
②Fine-tune the language model on those model answers using supervised learning—
③Rank the model's several answers to the same question. Train a separate reward model with this preference dataPeople choose which answer is better
④Adjust the language model in the direction that raises the scores the reward model assigns—
  • Step ③ is the key. Since people cannot score every answer one by one, we build a scorer that imitates human taste (the reward model) and have that scorer give the scores instead.
  • Connecting this to the reinforcement learning of Week 1, the difference is that the reward is given not by the environment but by a model that learned from human evaluations.

HITL Does Not Mean "People See Everything"

  • If people review every prediction, automation is pointless. The actual design is deciding the conditions for which cases get sent to people.
  • There are two representative conditions: cases where the model's confidence is below the threshold, and a randomly drawn sample for quality checks.

As a hypothetical example, a model that reads items from loan documents processes 10,000 per day. The 9,200 cases with confidence of 90% or higher pass straight through, and only the 800 cases (8%) below that are sent to a staff member. The staff member looks at just 8% of the total while still filtering out the cases most likely to be wrong. Blurry scans and hard-to-read handwriting mostly end up in these 800.

  • The AWS service that provides this structure is Amazon Augmented AI (Amazon A2I). It builds the flow that routes low-confidence predictions from Amazon Textract and Amazon Rekognition, or predictions from your own model, to human review (according to its documentation, A2I is also currently not open to new customers).
SituationSuitable human involvement
Tens of thousands of product photos need defect/normal markingData labeling (with automatic labeling alongside)
Labeling data that must not leak externally, such as medical imagesLabeling with a private workforce
Refining chatbot answers to be more helpful and less riskyHuman feedback (RLHF)
Checking only the low-confidence cases among document extraction resultsHITL review (confidence condition)
A high-impact decision such as a loan denialHITL — a person gives the final approval
Checking whether a model in operation is unfavorable to a specific groupHuman audit + subgroup analysis

Correcting Common Misconceptions

  • "HITL = people review every prediction" → Only the cases that are high risk or that the model is unsure about are selected and sent.
  • "If you use automatic labeling, people are not needed" → People label the initial sample and the low-confidence cases. The human workload merely shrinks.
  • "Unsupervised learning needs no people" → It just doesn't need labels. People interpret and verify whether the results are usable.
  • "Adding more labelers automatically raises quality" → If the guidelines are ambiguous, each person labels differently. Clear labeling criteria and review come first.
  • "A person reviewed it, so there is no bias" → Human judgment has bias too, and if it enters the labels, the model learns it as is.

Tomorrow we bring together everything from this week — the ML lifecycle and data — for a review and organize the points the exam asks about.

📖 Glossary

  • Data labeling: The work of people attaching a "this is what" correct answer to raw data.
  • Label: The answer key attached to data. The value the model uses as its reference when learning.
  • Supervised learning: A way of learning from data in which inputs and correct answers are paired. Labels are essential.
  • Unsupervised learning: A way of learning by looking only at the structure or groupings of the data itself, without answers.
  • RLHF: A technique in which people evaluate how good or bad the model's answers are, and the model is adjusted by that evaluation in the direction people want.
  • Human-in-the-loop (HITL): A design that doesn't let AI decide alone and inserts human judgment at important points.
  • Responsible AI: A collective term for the principles and practices that aim to make AI fair, safe, and explainable.
  • Amazon SageMaker Ground Truth: An AWS labeling service that manages human labelers and also helps with automatic labeling.
  • Iterative improvement: Making a model a little better by continually cycling through deploy → observe usage results → incorporate labels and feedback → retrain.
  • Label agreement: How often the same answer was attached when several people labeled the same data. A way of measuring label quality.

📝 Practice Questions

Click a choice to reveal the answer and explanation.

Question 1

In supervised learning, what is the task of attaching correct answers such as "this is a cat/dog" to data by humans called?

Question 2

Which technique is representative for refining a large language model (generative AI) in the direction humans prefer, by having humans rate the model's responses and reflecting those ratings in training?

Question 3

What is the approach called in which, for high-stakes decisions that greatly affect people's lives such as loan denials, AI does not make the decision on its own but is designed so that a human gives final review and approval?

Question 4

Which statement most accurately describes the effect of data labeling quality on a model?

Question 5

What is the most appropriate rebuttal to the claim that "once a model is built well, no more human involvement is needed"?

PreviousModel Evaluation Basics: Accuracy, Precision, Recall, and Overfitting/UnderfittingWeek 2 · Day 3Next Week 2 Wrap-Up: ML Lifecycle and Data at a GlanceWeek 2 · Day 5

Official references

  • AIF-C01 official exam page(opens in a new tab)
  • Amazon SageMaker AI documentation(opens in a new tab)

On this page

  • Key Takeaways
  • Why People Are Needed
  • 1. Data Labeling — Attaching Correct Answers
  • 2. Feedback — Evaluating and Correcting the Model's Answers
  • 3. Human-in-the-loop — A Person Is Inside the Loop
  • 4. Iterative Improvement — ML Is Not Completed in One Go
  • Labeling, Feedback, and Review Happen at Different Points in Time
  • How Does SageMaker Ground Truth Lighten the Human Workload?
  • In What Order Does RLHF Proceed?
  • HITL Does Not Mean "People See Everything"
  • Correcting Common Misconceptions
  • Glossary
  • Practice Questions