Triple
T33588237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSRC |
E860348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicular communication standard |
C2787
|
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: vehicular communication standard Context triple: [DSRC, instanceOf, vehicular communication standard]
-
A.
smartphone-to-car connectivity standard
A smartphone-to-car connectivity standard defines the protocols and interfaces that allow mobile devices to seamlessly integrate with and control in-vehicle systems for communication, media, navigation, and diagnostics.
-
B.
EV charging communication standard
A standardized set of protocols and message formats that enable interoperable, secure communication between electric vehicles, charging stations, and backend systems for managing charging sessions and related services.
-
C.
telecommunications standard
chosen
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
D.
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.
-
E.
SAE J3016 automation level
SAE J3016 automation level is a standardized classification that defines the degree of driving automation in vehicles, ranging from no automation (Level 0) to full automation (Level 5), based on the roles of the human driver and the automated driving system.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.