Triple
T38491082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FordPass Connect |
E918053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | connected vehicle system |
C16727
|
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: connected vehicle system Context triple: [FordPass Connect, instanceOf, connected vehicle system]
-
A.
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.
-
B.
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.
-
C.
shared vehicle architecture
A shared vehicle architecture is a common, modular platform designed to support multiple vehicle models or types, enabling reuse of components, streamlined engineering, and reduced development costs.
-
D.
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.
-
E.
vehicle companion app
chosen
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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.