Triple
T11416840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Category A listed building |
E270513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage building classification |
C11822
|
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 classification Context triple: [Category A listed building, instanceOf, heritage building classification]
-
A.
Historical building type
A historical building type is a category of structures defined by shared architectural features, construction methods, and cultural functions characteristic of a specific historical period or tradition.
-
B.
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.
-
C.
heritage register entry
chosen
A heritage register entry is an official record documenting the identification, significance, legal status, and key attributes of a place, object, or tradition recognized for its cultural or historical heritage value.
-
D.
serial heritage property
A serial heritage property is a collection of two or more geographically separate but related heritage components that together express a single, coherent cultural or natural significance.
-
E.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.