Triple
T13077710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabale |
E329619
|
entity |
| Predicate | hasLanguageSpoken |
P741
|
FINISHED |
| Object | Runyankole-Rukiga |
E275007
|
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: Runyankole-Rukiga | Statement: [Kabale, hasLanguageSpoken, Runyankole-Rukiga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runyankole-Rukiga Context triple: [Kabale, hasLanguageSpoken, Runyankole-Rukiga]
-
A.
Runyankole
chosen
Runyankole is a Bantu language spoken primarily by the Banyankole people in southwestern Uganda.
-
B.
Rukiga
Rukiga is a Bantu language spoken primarily by the Bakiga people in southwestern Uganda.
-
C.
Lega-Mwenga
Lega-Mwenga is a Bantu language variety spoken by the Lega people in the Democratic Republic of the Congo.
-
D.
Cyangugu
Cyangugu is a city in western Rwanda that serves as a key lakeside settlement and border crossing with the Democratic Republic of the Congo.
-
E.
Rumuokwurusi
Rumuokwurusi is a prominent urban town in Rivers State, Nigeria, known for its commercial activity and strategic location within the Port Harcourt metropolitan area.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d60aaac48190b5b724a19cad5279 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9:01 p.m.