Triple
T15131729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Sense |
E361436
|
entity |
| Predicate | sensingTechnology |
P17204
|
FINISHED |
| Object | 60 GHz radar |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 60 GHz radar | Statement: [Motion Sense, sensingTechnology, 60 GHz radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensingTechnology Context triple: [Motion Sense, sensingTechnology, 60 GHz radar]
-
A.
sensingDomain
Indicates the domain or context within which a sensing process, capability, or activity operates or is applicable.
-
B.
hasSensor
chosen
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
C.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
D.
trackingTechnology
Indicates that one entity uses or is associated with a technology designed to monitor, record, or follow the behavior, location, or interactions of another entity.
-
E.
targetSense
Indicates that one entity is the intended or actual target, focus, or endpoint of another entity’s action, attention, or effect.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.