Triple
T10294222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford platforms |
E241441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive platform family |
C9421
|
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 family Context triple: [Ford platforms, instanceOf, automotive platform family]
-
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.
vehicle platform
A vehicle platform is a shared structural and mechanical foundation, including chassis, powertrain, and key components, upon which multiple vehicle models can be built.
-
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.
Ford vehicle platform
chosen
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.
-
E.
automotive engine family
An automotive engine family is a group of closely related internal combustion engines that share a common basic design, architecture, and components but differ in specific parameters such as displacement, tuning, or fuel system to suit various vehicle applications.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:42 a.m.