AIQ
AIQ
Everything a teacher needs to deliver this lesson — pick your grade's script below once you've read the background.
By the end of this lesson, a student should be able to:
You don't need any AI or programming background to teach this lesson well. The core idea is simple: a sensor is a device that turns something physical into a number. A camera turns light into a grid of numbers (a digital image). A microphone turns air vibrations into a stream of numbers (an audio waveform). A thermometer turns heat into a number in degrees. None of that, by itself, is AI — it's just measurement. AI shows up later, in the software that looks at those numbers and finds a pattern, makes a prediction, or triggers a decision.
A useful way to frame this for any age: sensors are to a machine what sense organs are to a body. Your eyes don't "think" — they turn light into nerve signals, and your brain does the interpreting. A camera doesn't "think" either — it turns light into pixel values, and a computer vision program (a later lesson in this world) does the interpreting. This lesson is only about the first half of that chain: how the raw data gets collected in the first place. That's why the big idea for this world is Perception — before AI can reason about anything, it first has to sense it.
The lesson in the app walks students through three groups of sensors. First, the obvious ones: a camera (captures light as an image), a microphone (captures sound as vibration), a GPS receiver (uses satellite signals to fix a location, typically accurate to within a few meters), and a digital thermometer (reports temperature as a number, which is how smart-home systems automate heating and cooling). Second, the "hidden" sensors packed into a phone that students use daily without noticing: an accelerometer (detects motion and tilt — how the screen knows to rotate), a heart-rate sensor on a smartwatch (shines light through skin and measures how it bounces off blood flow), a touchscreen (detects the tiny electrical charge in a fingertip), and a digital compass (reads Earth's magnetic field to determine which way the device is facing). Third, the lesson shows what happens once AI is added on top of that raw data: a step counter uses AI to recognize the accelerometer's up-down pattern as "walking" rather than, say, "the phone was dropped." A self-driving car merges data from more than a dozen sensors at once. A smart farm system combines soil moisture, sunlight, and temperature readings to decide when to irrigate. A smart thermostat learns a household's schedule from temperature and motion history and adjusts on its own.
It's worth grounding this in devices your students actually carry. Almost every phone in a Filipino classroom already has the sensors this lesson describes, and apps students likely know make the idea concrete: a weather or PAGASA-linked app relies on GPS plus networked sensor data; a ride-hailing app like Grab tracks a car's GPS and accelerometer to estimate arrival time and detect hard braking; a banking or e-wallet app's face-verification step uses the camera as a sensor before any recognition happens. You don't need to demonstrate all of these — picking one that's locally familiar does more for retention than a longer list.
One accuracy point worth knowing before questions come up: sensors are never perfect. Consumer GPS is typically accurate to a few meters, not centimeters. Cameras struggle in poor light. Microphones pick up background noise along with the sound you want. This isn't a flaw specific to cheap devices — it's why systems that need to be reliable (like a self-driving car) combine several imperfect sensors rather than trusting one. That idea — sensor fusion — is introduced only lightly here and becomes more explicit in the two age bands built for older students.
It also helps to know where this lesson sits in the bigger picture, because a student will sometimes ask "so is this the AI part?" It isn't, quite. Collecting data through sensors is step one of what researchers call a perception pipeline: sense (a sensor captures raw physical data), digitize (that data becomes numbers a computer can store), find patterns (software looks across those numbers for something meaningful — a face, a spoken word, a walking rhythm), and decide or act (a system responds — unlocking a phone, transcribing speech, counting a step). This lesson lives almost entirely in the first two stages. The next two lessons in World 2 move into the third and fourth: how AI can be fooled even when its sensors are working correctly, and how vision, hearing, and reading come together in real products. You don't need to preview that content, but knowing the lesson's place in the sequence can help you answer a curious student who wants to know "when does the AI part actually happen?" — the honest answer is: right after this.
Finally, a note on scope for mixed-ability classes: the four age versions in the app differ mainly in vocabulary and how far into sensor fusion they go, not in the underlying facts. A single class period can accommodate students at different levels if you deliver the shared examples (camera, microphone, accelerometer, self-driving car) and let the discussion questions stretch further for students who are ready, rather than treating the age bands as strictly separate lesson plans.