Triple
T30209667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MirrorLink |
E768033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-vehicle infotainment connectivity technology |
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: in-vehicle infotainment connectivity technology Context triple: [MirrorLink, instanceOf, in-vehicle infotainment connectivity technology]
-
A.
in-vehicle infotainment platform
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 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.
-
C.
Smart vehicle
A smart vehicle is an automobile equipped with advanced sensors, connectivity, and automated systems that enable it to monitor its environment, assist or automate driving tasks, and communicate with other devices or infrastructure to enhance safety, efficiency, and user experience.
-
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.
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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:32 p.m.