Triple
T6327317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vehicle Navigation Systems |
E141892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | In-car electronic system |
C4490
|
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: In-car electronic system Context triple: [Vehicle Navigation Systems, instanceOf, In-car electronic system]
-
A.
in-vehicle infotainment platform
chosen
An in-vehicle infotainment platform is an integrated hardware and software system that delivers multimedia, navigation, connectivity, and vehicle information services through the car’s user interfaces.
-
B.
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.
-
C.
intelligent transportation system component
An intelligent transportation system component is a hardware or software element that collects, processes, or communicates transportation-related data to optimize traffic flow, enhance safety, and improve overall system efficiency.
-
D.
one-pedal driving system
A one-pedal driving system is a vehicle control feature that allows the driver to accelerate and decelerate using only the accelerator pedal by automatically applying regenerative and/or friction braking when the pedal is released.
-
E.
automotive all-wheel-drive system
An automotive all-wheel-drive system is a drivetrain configuration that automatically distributes engine power to all four wheels to enhance traction, stability, and handling across varying road and weather conditions.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.