Triple
T18368936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Heavy Industries |
E440128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Heavy machinery manufacturer |
C22106
|
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: Heavy machinery manufacturer Context triple: [Mitsubishi Heavy Industries, instanceOf, Heavy machinery manufacturer]
-
A.
heavy equipment manufacturer
chosen
A heavy equipment manufacturer is a company that designs, engineers, and produces large-scale machinery and vehicles used in construction, mining, agriculture, and other industrial applications.
-
B.
commercial vehicle manufacturer
A commercial vehicle manufacturer is a company that designs, produces, and sells vehicles intended primarily for business use, such as trucks, buses, and vans, to transport goods or passengers.
-
C.
manufacturing company
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
D.
armoured fighting vehicle manufacturer
An armoured fighting vehicle manufacturer is a company that designs, engineers, and produces military-grade, heavily protected combat vehicles such as tanks, infantry fighting vehicles, and armoured personnel carriers for armed forces and defense clients.
-
E.
rail transport manufacturer
A rail transport manufacturer is a company that designs, engineers, and produces railway vehicles and related equipment such as locomotives, passenger cars, freight wagons, and signaling systems.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:38 a.m.