Triple
T24396636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnStar Safety & Security |
E615044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | connected car service |
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 car service Context triple: [OnStar Safety & Security, instanceOf, connected car service]
-
A.
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.
-
B.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
-
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.
automotive data access API
An automotive data access API is a software interface that enables secure, standardized retrieval and manipulation of vehicle-related data—such as diagnostics, telematics, and configuration—from cars and associated backend systems.
-
E.
mobility services provider
A mobility services provider is an organization that offers and manages transportation solutions—such as ride-hailing, car-sharing, bike or scooter rentals, and integrated transit services—to enable people and goods to move efficiently from one place to another.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:04 a.m.