Triple
T34621641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resilient Heritage |
E889018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage funding programme |
C2057
|
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 funding programme Context triple: [Resilient Heritage, instanceOf, heritage funding programme]
-
A.
heritage funder
A heritage funder is an organization or individual that provides financial support to projects, institutions, or initiatives aimed at preserving, interpreting, and promoting cultural, historical, and natural heritage.
-
B.
heritage conservation programme
chosen
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.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
-
D.
heritage inventory program
A heritage inventory program is a systematic initiative to identify, document, and evaluate cultural, historical, and natural heritage resources within a defined area for their protection, management, and public awareness.
-
E.
heritage service
A heritage service is an organization or system dedicated to preserving, managing, and promoting cultural, historical, or natural heritage resources 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.