Triple
T29353918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busoga |
E744385
|
entity |
| Predicate | hasNumberOfTraditionalChiefdoms |
P192643
|
FINISHED |
| Object | 11 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 11 | Statement: [Busoga, hasNumberOfTraditionalChiefdoms, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfTraditionalChiefdoms Context triple: [Busoga, hasNumberOfTraditionalChiefdoms, 11]
-
A.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
B.
chiefdom
Indicates a hierarchical political relationship in which one central authority (a chief) holds primary power over a group or territory and its subordinate members or communities.
-
C.
hasTraditionalTerritoryType
Indicates that an entity’s traditional territory is classified as belonging to a specific type or category of territory.
-
D.
chiefdomName
Indicates that an entity has the name or title of a particular chiefdom.
-
E.
hasTraditionalRulers
Indicates that one entity possesses or is governed by traditional rulers associated with it.
- F. None of above. chosen
Provenance (4 batches)
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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 28, 2026, 2:09 p.m.