Triple
T37617226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural Mining and Metallurgical Company |
E935956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vertically integrated company |
C8157
|
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: vertically integrated company Context triple: [Ural Mining and Metallurgical Company, instanceOf, vertically integrated company]
-
A.
industrial holding company
An industrial holding company is a parent corporation that owns controlling interests in multiple industrial or manufacturing businesses, managing them strategically while typically leaving day-to-day operations to subsidiary management.
-
B.
integrated energy company
chosen
An integrated energy company is a business that operates across multiple stages of the energy value chain—such as exploration, production, refining, distribution, and retail—often spanning both fossil fuels and renewable energy sources.
-
C.
Conglomerate
A conglomerate is a large corporation composed of diverse, often unrelated businesses or subsidiaries managed under a single corporate group.
-
D.
publicly traded holding company
A publicly traded holding company is a corporation whose primary business is owning controlling interests in other companies, with its shares available for purchase on public stock exchanges.
-
E.
business holding company
A business holding company is a legal entity that owns controlling interests in other companies’ shares or assets, primarily to manage, oversee, and coordinate their operations and strategic direction without directly producing goods or services itself.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.