Triple
T8326824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Group MQB platform |
E194974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | modular platform |
C10283
|
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: modular platform Context triple: [Volkswagen Group MQB platform, instanceOf, modular platform]
-
A.
embedded software platform
An embedded software platform is an integrated collection of software components, tools, and runtime services that provide a standardized environment for developing, deploying, and managing applications on resource-constrained embedded devices.
-
B.
automotive platform
chosen
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.
-
C.
Supply-side platform
A supply-side platform is a technology system that helps digital publishers manage, optimize, and automate the selling of their advertising inventory across multiple ad exchanges and demand sources.
-
D.
middleware platform
A middleware platform is a software layer that sits between applications and underlying systems to provide common services, integration, and communication capabilities across distributed environments.
-
E.
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.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.