Triple
T13241673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAN bus |
E315294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive network technology |
C2279
|
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: automotive network technology Context triple: [CAN bus, instanceOf, automotive network technology]
-
A.
automotive manufacturing network
An automotive manufacturing network is an interconnected system of facilities, suppliers, logistics providers, and assembly plants that collaboratively design, produce, and deliver vehicles and components across regions or globally.
-
B.
Automotive technology
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.
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.
-
D.
network technology
chosen
Network technology encompasses the hardware, software, and protocols that enable devices and systems to connect, communicate, and exchange data over local and wide-area networks, including the internet.
-
E.
automotive platform
An automotive platform is a shared, standardized set of structural, mechanical, and electronic components that underpins multiple vehicle models to streamline development, reduce costs, and enable design flexibility.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:23 p.m.