Triple
T35741547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Assist driver assistance system |
E1033046
|
entity |
| Predicate | sensorInput |
P17204
|
FINISHED |
| Object | camera |
—
|
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: camera | Statement: [Pilot Assist driver assistance system, sensorInput, camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorInput Context triple: [Pilot Assist driver assistance system, sensorInput, camera]
-
A.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
B.
sensorClass
Indicates that one entity is classified as a type or category of sensor relative to another entity.
-
C.
hasSensor
chosen
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
D.
sensorProvider
Indicates that one entity serves as the source or supplier of sensor data or sensing capabilities for another entity.
-
E.
basicSense
Indicates that one entity represents the most fundamental or primary meaning or interpretation of another entity.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.