Triple
T29374136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mining heritage of Neves-Corvo area |
E744941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mining heritage |
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: mining heritage Context triple: [mining heritage of Neves-Corvo area, instanceOf, mining heritage]
-
A.
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.
-
B.
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.
-
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.
mining landscape
A mining landscape is a terrain significantly altered by the extraction of minerals or other geological resources, characterized by features such as open pits, spoil heaps, tailings ponds, and associated industrial infrastructure.
-
E.
mining industry
The mining industry encompasses the exploration, extraction, processing, and sale of minerals and other geological materials from the earth to supply raw inputs for manufacturing, energy production, and infrastructure.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:29 p.m.