Triple
T28957688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Monuments Service |
E731209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage protection body |
C5788
|
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 protection body Context triple: [National Monuments Service, instanceOf, heritage protection body]
-
A.
heritage conservation organization
chosen
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.
cultural heritage organisation
A cultural heritage organisation is an institution dedicated to preserving, managing, and promoting tangible and intangible cultural assets—such as artifacts, traditions, sites, and knowledge—for the benefit of present and future generations.
-
C.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
-
D.
heritage preserve
A heritage preserve is a protected area designated to conserve and manage significant natural, cultural, or historical resources for present and future generations.
-
E.
heritage protection system element
A heritage protection system element is a component—such as a policy, structure, technology, or procedure—designed to prevent damage, loss, or degradation of cultural or natural heritage assets.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:48 a.m.