Triple
T26377769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperVision |
E660945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | advanced driver-assistance system platform |
C10854
|
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 system platform Context triple: [SuperVision, instanceOf, advanced driver-assistance system platform]
-
A.
advanced driver-assistance system
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.
automotive platform
An automotive platform is a shared, standardized set of structural, mechanical, and electronic components that underpins multiple vehicle models to streamline development, reduce costs, and enable design flexibility.
-
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.
automotive computing platform
chosen
An automotive computing platform is an integrated hardware and software system within a vehicle that manages and coordinates functions such as infotainment, driver assistance, connectivity, and vehicle control in a secure and real-time manner.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 11:02 p.m.