Triple
T22098339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innlandet og Trøndelag mining region (historical) |
E546098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical mining region |
C4884
|
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: historical mining region Context triple: [Innlandet og Trøndelag mining region (historical), instanceOf, historical mining region]
-
A.
historic mining region
chosen
A historic mining region is an area where past extraction of minerals or ores significantly shaped its landscape, economy, culture, and built heritage, often leaving behind distinctive industrial sites and communities.
-
B.
copper-mining district
A copper-mining district is a geographically defined area characterized by the concentration of copper ore deposits and the associated mining, processing, and support activities that exploit them.
-
C.
historic mining complex
A historic mining complex is an integrated ensemble of former extraction, processing, and support facilities, structures, and landscapes that together illustrate the technological, economic, and social history of past mining activities.
-
D.
former mining town
A former mining town is a community that once relied heavily on mineral extraction as its primary economic activity but has since seen its mines close, often leading to economic, social, and environmental transitions.
-
E.
prehistoric mining site
A prehistoric mining site is an archaeological location where early human communities extracted raw materials such as stone, minerals, or metals using primitive tools and techniques before the advent of written records.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:30 p.m.