Triple
T38404527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novokramatorsky Mashinostroitelny Zavod |
E900987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavy engineering plant |
C4731
|
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 engineering plant Context triple: [Novokramatorsky Mashinostroitelny Zavod, instanceOf, heavy engineering plant]
-
A.
industrial plant
An industrial plant is a large-scale facility where raw materials are transformed through mechanical, chemical, or biological processes into finished or semi-finished products using specialized equipment and coordinated operations.
-
B.
manufacturing plant
chosen
A manufacturing plant is a large-scale industrial facility where raw materials are transformed through organized processes, machinery, and labor into finished goods or components.
-
C.
heavy equipment manufacturer
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.
-
D.
integrated steel mill
An integrated steel mill is a large industrial complex that converts raw materials like iron ore, coal, and limestone into finished steel products through a continuous, vertically integrated process including coke making, ironmaking, steelmaking, and rolling.
-
E.
heavy conversion unit
A heavy conversion unit is an industrial processing system designed to transform dense, low-value feedstocks into lighter, higher-value products through high-severity thermal and/or catalytic operations.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.