Triple
T25004761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coal Loader Centre for Sustainability |
E625810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage industrial site |
C28696
|
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: heritage industrial site Context triple: [Coal Loader Centre for Sustainability, instanceOf, heritage industrial site]
-
A.
industrial site
An industrial site is a designated area of land developed and equipped with infrastructure and facilities for manufacturing, processing, storage, or other large-scale industrial operations.
-
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.
heritage asset
chosen
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.
-
E.
transnational industrial heritage context
A transnational industrial heritage context is a cross-border framework that recognizes, interprets, and manages historically significant industrial sites, landscapes, and practices whose development, impact, and legacy extend beyond the boundaries of a single nation.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:05 a.m.