Triple
T9994437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcupine mining camp |
E196967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic mining camp |
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 camp Context triple: [Porcupine mining camp, instanceOf, historic mining camp]
-
A.
historic mining complex
chosen
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.
-
B.
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.
-
C.
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.
-
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.
historic industrial complex
A historic industrial complex is a large-scale, often multi-building site where past manufacturing, processing, or extractive activities took place, retaining significant architectural, technological, and cultural heritage value.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.