Triple
T13077699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabale |
E329619
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | Kisoro |
E341842
|
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: Kisoro | Statement: [Kabale, roadConnection, Kisoro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kisoro Context triple: [Kabale, roadConnection, Kisoro]
-
A.
Kisoro
chosen
Kisoro is a small town in southwestern Uganda known as a gateway to gorilla trekking and the nearby Bwindi Impenetrable and Mgahinga Gorilla National Parks.
-
B.
Kibondo
Kibondo is a town in western Tanzania that serves as an administrative and commercial center in the Kigoma Region.
-
C.
Nakasongola
Nakasongola is a town in central Uganda that serves as an administrative and commercial center for the surrounding rural district.
-
D.
Monguno
Monguno is a town and local government area in Borno State, northeastern Nigeria, known for its strategic location and role in regional security dynamics.
-
E.
Gokwe
Gokwe is a town in central Zimbabwe known for its cotton farming and role as a commercial hub in the Midlands Province.
- 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.