Triple
T21483140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mpumalanga provincial heritage authorities |
E530045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial 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: provincial heritage authority Context triple: [Mpumalanga provincial heritage authorities, instanceOf, provincial 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.
national heritage agency
A national heritage agency is a government body responsible for identifying, protecting, managing, and promoting a country’s cultural and natural heritage assets.
-
C.
provincial reserve
A provincial reserve is a protected natural area designated and managed by a provincial or regional government to conserve ecosystems, wildlife, and natural resources while often allowing limited public recreation and education.
-
D.
cultural heritage designation
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
-
E.
archaeological park authority
An archaeological park authority is an organization responsible for managing, protecting, researching, and presenting archaeological sites and their surrounding landscapes for public benefit and heritage conservation.
- F. None of above. chosen
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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:21 p.m.