Triple
T15131723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Sense |
E361436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radar-based gesture recognition technology |
C26080
|
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: radar-based gesture recognition technology Context triple: [Motion Sense, instanceOf, radar-based gesture recognition technology]
-
A.
3D radar
A 3D radar is a sensing system that measures the range, direction, and elevation of targets to provide a three-dimensional representation of their position in space.
-
B.
multi-mode radar
A multi-mode radar is a radar system capable of operating in several distinct modes (such as search, tracking, mapping, and weather detection) to support diverse sensing and mission requirements.
-
C.
pulse-Doppler radar
A pulse-Doppler radar is a radar system that transmits pulses of radio energy and uses the Doppler shift of returned echoes to simultaneously determine target range and relative velocity, enabling effective detection of moving targets in the presence of clutter.
-
D.
Motion-sensing device
chosen
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.
radar system family
A radar system family is a group of related radar systems that share a common architecture, technology base, and design principles while differing in specific capabilities, configurations, or applications.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:06 a.m.