Triple
T2274063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford D2C platform (fifth generation) |
E50727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rear-wheel-drive vehicle architecture |
C9310
|
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: rear-wheel-drive vehicle architecture Context triple: [Ford D2C platform (fifth generation), instanceOf, rear-wheel-drive vehicle architecture]
-
A.
wheel arrangement classification system
A wheel arrangement classification system is a conceptual framework that categorizes vehicles or rolling stock based on the number, configuration, and functional roles of their wheels or axles.
-
B.
autonomous robotic vehicle
An autonomous robotic vehicle is a self-navigating mobile machine that perceives its environment, makes decisions, and moves without direct human control.
-
C.
two-wheeled vehicle
A two-wheeled vehicle is a mode of transportation that balances and moves on two wheels, typically powered by human effort or a motor, and steered by handlebars.
-
D.
automotive architecture portfolio
An automotive architecture portfolio is a curated collection of design projects, drawings, models, and visual narratives that showcase a designer’s conceptual thinking, technical skills, and aesthetic approach to the spatial, structural, and experiential aspects of vehicles.
-
E.
sport utility vehicle
A sport utility vehicle is a versatile passenger vehicle that combines elements of on-road cars and off-road trucks, typically offering higher ground clearance, spacious interiors, and optional all-wheel or four-wheel drive for varied driving conditions.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:48 p.m.