Triple
T21032003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Landmark Trust |
E518086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | building conservation charity |
C5566
|
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: building conservation charity Context triple: [The Landmark Trust, instanceOf, building conservation charity]
-
A.
heritage conservation organization
A heritage conservation organization is an entity dedicated to identifying, protecting, preserving, and promoting cultural, historical, and natural heritage resources for present and future generations.
-
B.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
C.
church rebuilding project
A church rebuilding project is a coordinated effort to restore, reconstruct, or significantly renovate a church’s physical structure and facilities, often driven by structural needs, historical preservation, or community growth.
-
D.
historic preservation organization
chosen
A historic preservation organization is a group dedicated to identifying, protecting, and promoting buildings, sites, and artifacts of historical, cultural, or architectural significance.
-
E.
church restoration project
A church restoration project is an organized effort to repair, preserve, and sometimes modernize a church building while respecting and maintaining its historical, architectural, and spiritual 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:55 p.m.