Triple
T25535084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale smart locks |
E640020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet of Things device |
C50918
|
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: Internet of Things device Context triple: [Yale smart locks, instanceOf, Internet of Things device]
-
A.
Internet of Things platform
An Internet of Things platform is an integrated software and hardware environment that connects, manages, and analyzes data from distributed IoT devices to enable monitoring, control, and automation of physical systems.
-
B.
Internet of Things company
An Internet of Things company designs, develops, and manages connected devices and platforms that collect, exchange, and analyze data over networks to deliver automated, intelligent services.
-
C.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
D.
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.
-
E.
low-power networking platform
A low-power networking platform is a hardware and software system designed to enable energy-efficient, often battery-operated devices to communicate reliably over constrained wireless or wired networks.
- F. None of above. chosen
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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:22 p.m.