Triple
T29526959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakville Assembly Complex |
E749093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ford manufacturing plant |
C4810
|
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 manufacturing plant Context triple: [Oakville Assembly Complex, instanceOf, Ford manufacturing plant]
-
A.
General Motors factory
A General Motors factory is a large-scale automotive manufacturing facility where GM designs, assembles, and tests vehicles and related components using industrial machinery, robotics, and human labor.
-
B.
automobile factory
An automobile factory is a large-scale industrial facility where raw materials and components are systematically assembled, tested, and finished into complete motor vehicles using coordinated machinery, labor, and production processes.
-
C.
Toyota Motor Corporation facility
A Toyota Motor Corporation facility is any physical site owned or operated by Toyota where activities such as vehicle manufacturing, research and development, logistics, administration, sales, or service are conducted in support of the company’s automotive business.
-
D.
Tesla factory
A Tesla factory is a large-scale, highly automated manufacturing facility where Tesla designs, produces, and assembles electric vehicles and related components such as batteries and powertrains.
-
E.
automotive factory
chosen
An automotive factory is a large-scale industrial facility where vehicles and their components are systematically designed, manufactured, assembled, and tested using specialized machinery, robotics, and human labor.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:47 p.m.