Triple
T16067874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Motor Manufacturing Texas |
E389778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toyota manufacturing plant |
C32386
|
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: Toyota manufacturing plant Context triple: [Toyota Motor Manufacturing Texas, instanceOf, Toyota manufacturing plant]
-
A.
Toyota Motor Corporation facility
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Honda vehicle
A Honda vehicle is a motorized transportation product manufactured by Honda, designed to provide reliable, efficient, and user-friendly mobility for personal or commercial use.
-
E.
Honda executive
A Honda executive is a high-level decision-maker responsible for guiding the company’s strategic direction, overseeing operations and innovation, and ensuring sustainable growth in alignment with Honda’s global vision and values.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.