Triple
T4434038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Heavy Industries |
E95603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational conglomerate company |
C15000
|
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: multinational conglomerate company Context triple: [Mitsubishi Heavy Industries, instanceOf, multinational conglomerate company]
-
A.
Conglomerate
chosen
A conglomerate is a large corporation composed of diverse, often unrelated businesses or subsidiaries managed under a single corporate group.
-
B.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
-
C.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
D.
multinational commodity trading and mining company
A multinational commodity trading and mining company is a global enterprise that extracts raw materials from diverse geographic locations and markets, transports, and trades them across international supply chains to industrial and financial customers.
-
E.
media and telecommunications conglomerate
A media and telecommunications conglomerate is a large corporate entity that owns and operates a diverse portfolio of media, entertainment, and communication businesses across multiple platforms and markets.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:31 p.m.