Triple
T3738884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix platform (derived from Saab technology) |
E79651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive vehicle 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: automotive vehicle platform Context triple: [Phoenix platform (derived from Saab technology), instanceOf, automotive vehicle platform]
-
A.
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.
-
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.
Ford vehicle platform
A Ford vehicle platform is a shared engineering and structural foundation used across multiple Ford models to standardize components, reduce costs, and streamline design and production.
-
D.
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.
-
E.
General Motors platform
A General Motors platform is a shared underlying vehicle architecture, including structural, mechanical, and sometimes electronic components, used across multiple GM models to streamline design, production, and costs.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.