Triple
T535899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Model e |
E12326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive division |
C3967
|
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 division Context triple: [Ford Model e, instanceOf, automotive division]
-
A.
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.
-
B.
Ford Motor Company division
chosen
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.
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.
-
D.
automotive terminal
An automotive terminal is an electrical connector component used in vehicles to securely join wires to each other or to devices within the automotive electrical system.
-
E.
defense contractor division
A defense contractor division is an organizational unit within a defense company responsible for developing, producing, and supporting specific military or security-related products, services, or programs for government and allied clients.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.