Triple
T18074157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Bunyoro |
E432509
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Bunyoro-Kitara |
—
|
NE NERFINISHED |
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: Bunyoro-Kitara | Statement: [Kingdom of Bunyoro, historicalName, Bunyoro-Kitara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bunyoro-Kitara Context triple: [Kingdom of Bunyoro, historicalName, Bunyoro-Kitara]
-
A.
Bunyoro
chosen
Bunyoro is a traditional kingdom and historical region in western Uganda that was once a powerful pre-colonial African state.
-
B.
Rubanda District
Rubanda District is an administrative district in southwestern Uganda known for its hilly terrain and rural communities.
-
C.
Kasese
Kasese is a town in western Uganda that serves as a key gateway to Queen Elizabeth National Park and the Rwenzori Mountains.
-
D.
Kiryandongo
Kiryandongo is a town in western Uganda that serves as the administrative and commercial center of Kiryandongo District.
-
E.
Runyankole
Runyankole is a Bantu language spoken primarily by the Banyankole people in southwestern Uganda.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ccefcdc4819086d0b224731bfc4d |
completed | April 19, 2026, 12:39 p.m. |
Created at: April 10, 2026, 10:26 a.m.