Triple
T18074254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buganda Land Board |
E432512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land management institution |
C3836
|
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: land management institution Context triple: [Buganda Land Board, instanceOf, land management institution]
-
A.
land management agency
chosen
A land management agency is an organization responsible for planning, regulating, and overseeing the use, conservation, and development of public or private land resources.
-
B.
landscape management partnership
A landscape management partnership is a collaborative arrangement among diverse stakeholders—such as landowners, communities, governments, and NGOs—to plan, coordinate, and implement sustainable practices across a shared landscape for ecological, economic, and social benefits.
-
C.
natural resources management agency
A natural resources management agency is an organization responsible for planning, regulating, and overseeing the sustainable use, conservation, and restoration of natural resources such as land, water, forests, wildlife, and minerals.
-
D.
park management headquarters
The park management headquarters is a central facility where administrative staff coordinate operations, planning, and resource management for one or more parks.
-
E.
protected area management body
A protected area management body is an organization or authority responsible for planning, regulating, and overseeing the conservation, use, and monitoring of a designated protected area and its natural and cultural resources.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.