Triple
T21808929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Record of the Historic Environment entries |
E538420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic building record |
C45344
|
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: historic building record Context triple: [National Record of the Historic Environment entries, instanceOf, historic building record]
-
A.
historic architecture
Historic architecture encompasses buildings and structures from past eras that embody the cultural, technological, and artistic values of the time in which they were created.
-
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.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
D.
historic library building
A historic library building is a culturally significant, often architecturally distinctive structure originally designed to house and provide public access to collections of books and other knowledge resources.
-
E.
historic municipal building
A historic municipal building is a long-standing public structure, such as a city hall or courthouse, that has served governmental or civic functions and holds architectural, cultural, or historical significance for a community.
- F. None of above. chosen
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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.