Triple
T20680706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochore mining area |
E508283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former coal mining district |
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: former coal mining district Context triple: [Lochore mining area, instanceOf, former coal mining district]
-
A.
former coal-mining town
A former coal-mining town is a community whose historical development, economy, and identity were once centered on coal extraction but which now faces post-industrial transition, often marked by economic restructuring, environmental legacies, and evolving cultural narratives.
-
B.
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.
-
C.
former industrial town
A former industrial town is a community whose economy and identity were once dominated by manufacturing or heavy industry but have since declined or transitioned to other forms of economic activity.
-
D.
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.
-
E.
coal-mining city
A coal-mining city is an urban settlement whose economy, landscape, and community life are predominantly shaped by the extraction, processing, and transport of coal.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.