Triple
T11780882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheduled Monument |
E280141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic building designation |
C826
|
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 designation Context triple: [Scheduled Monument, instanceOf, historic building designation]
-
A.
historic designation
chosen
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
B.
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.
-
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.
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.
historic district contributing property
A historic district contributing property is a building, structure, site, or object within a designated historic district that adds to the district’s historical, architectural, or cultural significance.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:42 p.m.