Triple
T8585704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buganda |
E203300
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Luweero |
E746502
|
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: Luweero | Statement: [Buganda, contains, Luweero]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luweero Context triple: [Buganda, contains, Luweero]
-
A.
Luweero District
chosen
Luweero District is an administrative district in Uganda known for its role as a key battleground area during the Ugandan Bush War in the 1980s.
-
B.
Soroti
Soroti is a town in eastern Uganda that serves as a regional commercial and administrative center.
-
C.
Nimule
Nimule is a South Sudanese border town near Uganda that serves as a key trade and transport hub in the region.
-
D.
Kasese
Kasese is a town in western Uganda that serves as a key gateway to Queen Elizabeth National Park and the Rwenzori Mountains.
-
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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc457ab8b08190a53c730417288deb |
completed | March 31, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc7a6e28819090e988343be42a1b |
completed | April 2, 2026, 8:07 p.m. |
Created at: March 30, 2026, 6:22 p.m.