Triple
T13512744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valtion Metallitehtaat |
E322678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metal industry company |
C136
|
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: metal industry company Context triple: [Valtion Metallitehtaat, instanceOf, metal industry company]
-
A.
manufacturing company
chosen
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.
-
B.
materials science company
A materials science company researches, develops, and commercializes advanced materials and related technologies to improve the performance, efficiency, and sustainability of products across various industries.
-
C.
nuclear industry company
A nuclear industry company is an organization that designs, builds, operates, or services nuclear facilities and technologies for energy production, research, medicine, or defense while managing strict safety, regulatory, and environmental requirements.
-
D.
coal mining company
A coal mining company is an organization that explores for, extracts, processes, and sells coal resources, typically operating mines and related infrastructure while managing economic, environmental, and regulatory responsibilities.
-
E.
copper mining company
A copper mining company is a business entity that explores for, extracts, processes, and sells copper ore and related products, often managing large-scale mining operations and associated environmental and regulatory responsibilities.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.