Triple
T16288636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clipstone Colliery headstocks |
E395456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial heritage structure |
C8770
|
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: industrial heritage structure Context triple: [Clipstone Colliery headstocks, instanceOf, industrial heritage structure]
-
A.
historic industrial structure
chosen
A historic industrial structure is a preserved building or facility originally designed for manufacturing, processing, or other industrial activities, valued today for its architectural, technological, and cultural significance.
-
B.
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.
-
C.
historic industrial area
A historic industrial area is a district characterized by preserved or repurposed factories, warehouses, and infrastructure that reflect the industrial heritage and economic history of a place.
-
D.
former industrial plant
A former industrial plant is a decommissioned facility that once housed large-scale manufacturing or processing operations, often leaving behind substantial physical infrastructure and potential environmental impacts.
-
E.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.