Triple
T31238542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Powertrain Engineering |
E796493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive powertrain organization |
C59377
|
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 powertrain organization Context triple: [Ford Powertrain Engineering, instanceOf, automotive powertrain organization]
-
A.
hybrid powertrain technology
Hybrid powertrain technology integrates an internal combustion engine with one or more electric motors and a battery system to optimize fuel efficiency, reduce emissions, and enhance vehicle performance through intelligent power management.
-
B.
drivetrain technology
Drivetrain technology encompasses the systems and components that transmit power from a vehicle’s engine or motor to its wheels, optimizing efficiency, performance, and control.
-
C.
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.
-
D.
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.
-
E.
automotive all-wheel-drive system
An automotive all-wheel-drive system is a drivetrain configuration that automatically distributes engine power to all four wheels to enhance traction, stability, and handling across varying road and weather 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:11 p.m.