Triple
T8585686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buganda |
E203300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional kingdom |
C10492
|
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: traditional kingdom Context triple: [Buganda, instanceOf, traditional kingdom]
-
A.
pre-colonial kingdom
chosen
A pre-colonial kingdom is a sovereign political entity that existed before foreign colonial rule, typically characterized by indigenous governance structures, distinct cultural traditions, and control over defined territories and populations.
-
B.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
C.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
D.
traditional homeland
A traditional homeland is a geographic area historically inhabited, used, and culturally identified with by an Indigenous or long-established community, forming the core of its ancestral identity and way of life.
-
E.
traditional state
A traditional state is a political entity whose authority and social order are grounded in long-standing customs, inherited institutions, and historically established power structures rather than modern legal-rational frameworks.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:22 p.m.