TEACHER ONLY · LESSON GUIDE
Picture This Day 3 — Be the AI
Use this page to run the lesson. The student item directly below remains the independent and absence route.
Daily Learning Contract
Topic: Classification rules and dataset bias
Objective: Students will analyze how visible classification rules and gaps in training data affect predictions on new examples.
- §126.19(c)(3)(B) — discuss and implement a design process that includes planning, selecting digital tools to develop, test, and evaluate design limitations, and refining a prototype or model; and
- §126.19(c)(6) — The student uses digital tools to transform data, make inferences, and predictions. The student is expected to use digital tools in order to transform data, analyze trends, and predict possibilities and develop steps for the creation of an innovative process or product.
Demonstration of learning: Written classification rules, test results from the bias-test images, and an exit explanation naming the learned pattern and the rule or data gap.
Before class
Time: One class period
Student route:
Day 3 · Be the AI: Rules, Data, and Bias
Use what already exists: Day 3 deck; cat/dog datasets; bias-test photos; exit ticket; scissors and glue/tape.
Lesson flow
- Launch: Start with a quick image-sort prediction.
- Model: Model a visible classification rule that fails on an edge case.
- Do: Teams sort, write rules, and test with the bias-test photos.
- Check + support: Check that students name a missing pattern rather than a vague error; use rule stems and visual categories.
- Close + handoff: Collect the exit ticket and bridge to training a more reliable model.
Check before students leave
Ask each student or team to point to the specific evidence named above and explain one choice, test, or revision. Completion alone is not evidence of understanding.
Support + troubleshooting
Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.
When stuck: Ask students to show the exact step where the system stopped, then check setup, inputs, and saved work before replacing the task.