Triple
T15689231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uconnect infotainment system |
E380281
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infotainment 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: infotainment system Context triple: [Uconnect infotainment system, instanceOf, infotainment 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.
proprietary entertainment system
A proprietary entertainment system is a closed, vendor-controlled platform that delivers media or interactive content using exclusive hardware, software, or formats not fully compatible with open or competing systems.
-
C.
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.
-
D.
digital instrument cluster
A digital instrument cluster is an electronic display system in a vehicle that replaces traditional analog gauges to present real-time driving information such as speed, RPM, fuel level, and warnings in a customizable, often graphical format.
-
E.
vehicle companion app
A vehicle companion app is a mobile application that connects to a vehicle to provide real-time status, remote control features, trip information, and maintenance insights to the driver.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:44 a.m.