Triple
T13188094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand facade |
E313911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage building element |
C25050
|
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 building element Context triple: [East Stand facade, instanceOf, heritage building element]
-
A.
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.
-
B.
historic building section
A historic building section is a vertical cut-through representation of an older, culturally or architecturally significant structure that reveals its internal organization, construction methods, and spatial relationships over time.
-
C.
cultural heritage element
chosen
A cultural heritage element is a tangible or intangible manifestation of a community’s traditions, practices, expressions, knowledge, or artifacts that is valued, preserved, and transmitted across generations.
-
D.
architecturally significant building
An architecturally significant building is a structure whose design, innovation, historical importance, or cultural impact distinguishes it as notably influential or exemplary within the built environment.
-
E.
ancient building
An ancient building is a historically significant structure from antiquity, often characterized by enduring construction materials, distinctive architectural styles, and cultural or archaeological importance.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:15 p.m.