Triple
T21483142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mpumalanga provincial heritage authorities |
E530045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage resources authority |
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 resources authority Context triple: [Mpumalanga provincial heritage authorities, instanceOf, heritage resources authority]
-
A.
historic environment service
A historic environment service is an organization or unit that identifies, protects, manages, and promotes understanding of historic buildings, archaeological sites, and cultural landscapes within a given area.
-
B.
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.
-
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 centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
-
E.
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.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:21 p.m.