Triple
T19398030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACC |
E485243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | advanced driver-assistance feature |
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: advanced driver-assistance feature Context triple: [TACC, instanceOf, advanced driver-assistance feature]
-
A.
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.
-
B.
driver feature
A driver feature is a specific functionality or characteristic of a driver (software or person) that enables, enhances, or customizes the operation, control, or performance of a vehicle or hardware system.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:36 p.m.