Triple
T13930256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Orme Copper Mines |
E334970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric copper mine |
C18264
|
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: prehistoric copper mine Context triple: [Great Orme Copper Mines, instanceOf, prehistoric copper mine]
-
A.
prehistoric mining site
chosen
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.
-
B.
copper mine
A copper mine is an industrial site where copper ore is extracted from the earth, processed, and refined for use in manufacturing and construction.
-
C.
prehistoric underground burial complex
A prehistoric underground burial complex is a network of subterranean chambers and passages constructed by ancient societies to inter the dead, often accompanied by ritual artifacts and symbolic architecture.
-
D.
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.
-
E.
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.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.