Triple
T2199349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Fox platform (third generation) |
E50452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ford vehicle platform |
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: Ford vehicle platform Context triple: [Ford Fox platform (third generation), instanceOf, Ford vehicle platform]
-
A.
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.
-
B.
Ford Motor Company division
A Ford Motor Company division is an organizational unit within Ford responsible for specific product lines, markets, or business functions, operating under the broader corporate structure and strategy of the company.
-
C.
automotive brand
An automotive brand is a conceptual entity representing the identity, reputation, and market presence of a manufacturer that designs, produces, and sells motor vehicles under a distinct name and image.
-
D.
automobile model
An automobile model is a specific version of a vehicle produced by a manufacturer, defined by a distinct combination of design, features, and specifications that differentiates it from other vehicles in the product lineup.
-
E.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
- F. None of above. chosen
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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.