Triple
T23103517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford global platform strategy |
E576096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive engineering strategy |
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 engineering strategy Context triple: [Ford global platform strategy, instanceOf, automotive engineering strategy]
-
A.
automobile design
Automobile design is the conceptual and aesthetic process of creating a vehicle’s overall form, function, and user experience, integrating styling, ergonomics, engineering constraints, and brand identity.
-
B.
automotive architecture
Automotive architecture is the conceptual and structural design framework that defines how a vehicle’s key systems, components, and spatial layout are organized and integrated to meet performance, safety, and user experience goals.
-
C.
automobile design study
An automobile design study is a conceptual exploration and evaluation of vehicle form, function, and technology to guide the development of future production models.
-
D.
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.
-
E.
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.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:58 p.m.