Triple
T16195157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abertamy–Boží Dar–Horní Blatná mining landscape |
E393041
|
entity |
| Predicate | topLevelSiteOf |
P5003
|
FINISHED |
| Object | Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region |
E393041
|
NE FINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region | Statement: [Abertamy–Boží Dar–Horní Blatná mining landscape, topLevelSiteOf, Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region Context triple: [Abertamy–Boží Dar–Horní Blatná mining landscape, topLevelSiteOf, Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region]
-
A.
Abertamy–Boží Dar–Horní Blatná mining landscape
chosen
The Abertamy–Boží Dar–Horní Blatná mining landscape is a historic ore-mining area in the Ore Mountains of the Czech Republic, notable for its well-preserved mining towns, shafts, and related infrastructure that form part of the UNESCO-listed Erzgebirge/Krušnohoří Mining Region.
-
B.
Erzgebirge/Krušnohoří Mining Region
The Erzgebirge/Krušnohoří Mining Region is a transboundary UNESCO World Heritage cultural landscape along the German-Czech border, renowned for its centuries-long history of ore mining and its profound influence on mining technology, settlement patterns, and regional culture.
-
C.
Březové Hory mining district
Březové Hory mining district is a historic silver and lead mining area in Příbram, Czech Republic, known for its extensive underground workings and preserved mining heritage.
-
D.
Bohemia mining district
The Bohemia mining district is a historic gold- and silver-mining area in the Cascade Range of Oregon, known for its 19th- and early 20th-century mining activity and remaining ruins near Cottage Grove.
-
E.
Mansfeld mining district
The Mansfeld mining district is a historic copper shale mining region in central Germany that played a major role in the area’s industrial development from the Middle Ages into the 20th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelSiteOf Context triple: [Abertamy–Boží Dar–Horní Blatná mining landscape, topLevelSiteOf, Abertamy–Boží Dar–Horní Blatná component of Erzgebirge/Krušnohoří Mining Region]
-
A.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
B.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
C.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
-
D.
containsSite
chosen
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
E.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
- F. None of above.
Provenance (4 batches)
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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d851188190b2452d165e4fc4bd |
completed | April 17, 2026, 12:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff0f352081908324783743e47029 |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.