Triple
T16302642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyactiv technology |
E395829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive technology suite |
C20323
|
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: automotive technology suite Context triple: [Skyactiv technology, instanceOf, automotive technology suite]
-
A.
automotive architecture
Automotive architecture is the conceptual and structural design framework that defines how a vehicle’s key systems, components, and spatial layout are organized and integrated to meet performance, safety, and user experience goals.
-
B.
automotive computing platform
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.
-
C.
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.
-
D.
Automotive technology
chosen
Automotive technology encompasses the design, development, operation, and maintenance of motor vehicles and their supporting systems, including engines, electronics, safety features, and emerging innovations like electric and autonomous driving.
-
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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.