Triple
T11596233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runyankole |
E275007
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Runyankore |
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: Runyankore | Statement: [Runyankole, hasAlternativeName, Runyankore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runyankore Context triple: [Runyankole, hasAlternativeName, Runyankore]
-
A.
Soroti
Soroti is a town in eastern Uganda that serves as a regional commercial and administrative center.
-
B.
Runyankole
chosen
Runyankole is a Bantu language spoken primarily by the Banyankole people in southwestern Uganda.
-
C.
Lyantonde
Lyantonde is a town and district in central Uganda, situated within the traditional kingdom region of Buganda.
-
D.
Bukoto
Bukoto is a residential and commercial neighborhood in Kampala, Uganda, known for its mix of middle-class housing, local businesses, and proximity to several of the city’s prominent suburbs.
-
E.
Nyabira
Nyabira is a small town in northern Zimbabwe located within Mashonaland West Province, serving as a local commercial and residential center.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a7cad108819082eebb3ca130f5b8 |
completed | April 22, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:38 p.m.