Triple
T1381727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mines of Rammelsberg |
E29352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic mining complex |
C6816
|
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: historic mining complex Context triple: [Mines of Rammelsberg, instanceOf, historic mining complex]
-
A.
historic mining region
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.
historic blast furnace complex
A historic blast furnace complex is an industrial site, often preserved as heritage, where iron ore was once smelted at high temperatures in large furnaces along with associated structures such as casting houses, coke ovens, and worker facilities.
-
C.
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.
-
D.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
E.
historic infrastructure
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
- F. None of above. chosen
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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.