Triple
T27911314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Protect |
E705935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | smart smoke detector |
C2618
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: smart smoke detector Context triple: [Nest Protect, instanceOf, smart smoke detector]
-
A.
smart doorbell
A smart doorbell is an internet-connected doorbell system that uses sensors, a camera, microphone, and network connectivity to notify homeowners of visitors, enable two-way communication, and often provide video recording and integration with other smart home devices.
-
B.
detector
chosen
A detector is an entity that senses, identifies, or measures the presence or characteristics of specific signals, objects, or conditions within its environment.
-
C.
smart home ecosystem
A smart home ecosystem is an interconnected network of devices, sensors, and services within a home that communicate and coordinate to automate tasks, optimize energy use, enhance security, and improve residents’ comfort and convenience.
-
D.
smart home automation feature
A smart home automation feature is a software-controlled capability that coordinates connected devices and sensors to automatically manage household functions like lighting, climate, security, and appliances based on user preferences, schedules, and contextual triggers.
-
E.
Motion-sensing device
A motion-sensing device is a hardware component that detects and measures movement or changes in position within its environment, often using technologies like infrared, ultrasonic, or accelerometers to trigger responses or collect data.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:50 p.m.