Triple
T14692068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Wren churches in London |
E345058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural heritage ensemble |
C2724
|
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: architectural heritage ensemble Context triple: [Christopher Wren churches in London, instanceOf, architectural heritage ensemble]
-
A.
architectural ensemble
chosen
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
B.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
-
C.
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.
-
D.
artistic heritage site
An artistic heritage site is a location recognized for its enduring cultural, historical, and aesthetic value, preserving significant works of art, architecture, or creative traditions for present and future generations.
-
E.
palace and park ensemble
A palace and park ensemble is a unified architectural and landscape complex where a grand residence is integrated with designed gardens, water features, and surrounding grounds to form a cohesive cultural and aesthetic whole.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.