Triple
T14629497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW Driving Assistant Professional |
E343441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | semi-automated driving system |
C5178
|
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: semi-automated driving system Context triple: [BMW Driving Assistant Professional, instanceOf, semi-automated driving system]
-
A.
autonomous driving technology
Autonomous driving technology encompasses the hardware, software, and algorithms that enable vehicles to perceive their environment, make driving decisions, and control motion with minimal or no human intervention.
-
B.
advanced driver-assistance system
chosen
An advanced driver-assistance system is an integrated set of vehicle technologies that monitor the driving environment and vehicle status to assist the driver in controlling the car, enhancing safety, comfort, and efficiency.
-
C.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
D.
SAE J3016 automation level
SAE J3016 automation level is a standardized classification that defines the degree of driving automation in vehicles, ranging from no automation (Level 0) to full automation (Level 5), based on the roles of the human driver and the automated driving system.
-
E.
automotive safety system
An automotive safety system is an integrated set of components and technologies designed to prevent accidents or reduce injury and damage when collisions occur.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.