Triple
T5258525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukono |
E118761
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Buganda |
E203300
|
NE 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: Buganda | Statement: [Mukono, region, Buganda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buganda Context triple: [Mukono, region, Buganda]
-
A.
Buganda
chosen
Buganda is a traditional Bantu kingdom in central Uganda that is the country’s most populous and historically influential region.
-
B.
Nakasongola
Nakasongola is a town in central Uganda that serves as an administrative and commercial center for the surrounding rural district.
-
C.
Kanyaga
"Kanyaga" is a popular Tanzanian Bongo Flava hit song by Diamond Platnumz known for its energetic beat and danceable style.
-
D.
Bindura
Bindura is a town in northern Zimbabwe that serves as the administrative and commercial center of the surrounding mining and agricultural region.
-
E.
Kibondo
Kibondo is a town in western Tanzania that serves as an administrative and commercial center in the Kigoma Region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ba791c08190a18176feae8d1475 |
completed | March 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe821e3c8190a03c8aa581cc23cf |
completed | March 21, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:50 p.m.