Triple
T33435773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proximity Events |
E856235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sensor API |
C60480
|
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: sensor API Context triple: [Proximity Events, instanceOf, sensor API]
-
A.
depth sensor
A depth sensor is a device that measures the distance from itself to objects in its field of view, typically using technologies like time-of-flight, structured light, or stereo vision to produce depth information.
-
B.
environmental sensor suite
An environmental sensor suite is an integrated collection of sensors and supporting electronics designed to measure, process, and report multiple environmental parameters such as temperature, humidity, air quality, light, and pressure in a coordinated manner.
-
C.
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.
-
D.
magnetic field sensor
A magnetic field sensor is a device that detects and measures the strength and direction of magnetic fields, converting them into electrical signals for monitoring or control applications.
-
E.
Inertial measurement unit
An inertial measurement unit is a sensor device that measures and reports an object's specific force, angular rate, and sometimes magnetic field to determine its motion and orientation in space.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.