Triple
T13852475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyambura Gorge |
E332977
|
entity |
| Predicate | nearestMajorCity |
P1982
|
FINISHED |
| Object | Kasese |
E332728
|
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: Kasese | Statement: [Kyambura Gorge, nearestMajorCity, Kasese]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kasese Context triple: [Kyambura Gorge, nearestMajorCity, Kasese]
-
A.
Kasese
chosen
Kasese is a town in western Uganda that serves as a key gateway to Queen Elizabeth National Park and the Rwenzori Mountains.
-
B.
Soroti
Soroti is a town in eastern Uganda that serves as a regional commercial and administrative center.
-
C.
Mbale
Mbale is a major town in eastern Uganda, known as a commercial and administrative center near the slopes of Mount Elgon.
-
D.
Mbarara
Mbarara is a major city in southwestern Uganda that serves as a key commercial and transport hub for the region.
-
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 (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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd08c21a48190b4077d5acb4ab658 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:14 p.m.