Triple
T13526075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota New Global Architecture |
E323019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive platform architecture |
C14028
|
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 platform architecture Context triple: [Toyota New Global Architecture, instanceOf, automotive platform architecture]
-
A.
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.
-
B.
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.
-
C.
vehicle platform
chosen
A vehicle platform is a shared structural and mechanical foundation, including chassis, powertrain, and key components, upon which multiple vehicle models can be built.
-
D.
automobile platform code
An automobile platform code is a standardized identifier used by manufacturers to denote a shared underlying vehicle architecture, including chassis, structural components, and key systems, across multiple car models.
-
E.
electric vehicle platform
An electric vehicle platform is a modular, shared chassis architecture that integrates the battery pack, electric motors, suspension, and core electronics to serve as the foundation for multiple EV models.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.