Triple
T28662320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heritage authorities of Rhineland-Palatinate |
E725499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage authority |
C44846
|
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 authority Context triple: [heritage authorities of Rhineland-Palatinate, instanceOf, heritage authority]
-
A.
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.
-
B.
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.
-
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.
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.
provincial heritage authority
chosen
A provincial heritage authority is a government body responsible for identifying, protecting, managing, and promoting cultural and historical resources within a specific province or regional jurisdiction.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:59 a.m.