Triple
T14330142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google built-in (on many trims) |
E355323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-car software suite |
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 software suite Context triple: [Google built-in (on many trims), instanceOf, in-car software suite]
-
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 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.
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.
-
D.
vehicle platform
A vehicle platform is a shared structural and mechanical foundation, including chassis, powertrain, and key components, upon which multiple vehicle models can be built.
-
E.
automotive software company
A company that designs, develops, and maintains software solutions specifically for vehicles and the automotive industry, such as embedded systems, driver assistance, connectivity, and fleet management platforms.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.