Triple
T9606387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English in Uganda |
E231981
|
entity |
| Predicate | coexistsWith |
P1867
|
FINISHED |
| Object | Runyoro-Rutooro |
E695723
|
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: Runyoro-Rutooro | Statement: [English in Uganda, coexistsWith, Runyoro-Rutooro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runyoro-Rutooro Context triple: [English in Uganda, coexistsWith, Runyoro-Rutooro]
-
A.
Runyoro
chosen
Runyoro is a Bantu language spoken primarily by the Banyoro people in western Uganda.
-
B.
Rutooro
Rutooro is a Bantu language spoken primarily by the Tooro people in western Uganda.
-
C.
Swahili Wiktionary
Swahili Wiktionary is the Swahili-language edition of Wiktionary, a collaborative online dictionary and lexical resource for Swahili words and terms.
-
D.
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.
-
E.
Ngindo language
The Ngindo language is a Bantu language spoken by the Ngindo people of southeastern Tanzania.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a6006d48190adc03306533b9be6 |
completed | April 1, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d17939ed4c8190addfb052b762d454 |
completed | April 4, 2026, 8:48 p.m. |
Created at: March 30, 2026, 8:08 p.m.