Triple
T18368937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Heavy Industries |
E440128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Defense contractor |
C5343
|
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: Defense contractor Context triple: [Mitsubishi Heavy Industries, instanceOf, Defense contractor]
-
A.
defense industry holding company
A defense industry holding company is a corporate entity that owns and manages a portfolio of businesses involved in the research, development, production, and support of military and security-related products and services.
-
B.
defense company
chosen
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
C.
defense contractor business unit
A defense contractor business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or programs for government and allied customers.
-
D.
defense industry
The defense industry comprises organizations and companies that research, develop, produce, and maintain military equipment, technologies, and services for national security and defense purposes.
-
E.
defense industry business unit
A defense industry business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or technologies for government and allied customers.
- 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.