Triple
T16564052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chobe River |
E402410
|
entity |
| Predicate | adjacentToTown |
P44955
|
FINISHED |
| Object | Kasane |
E364999
|
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: Kasane | Statement: [Chobe River, adjacentToTown, Kasane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kasane Context triple: [Chobe River, adjacentToTown, Kasane]
-
A.
Kasane
chosen
Kasane is a small town in northern Botswana that serves as a key gateway and service hub for visitors to Chobe National Park and the surrounding wildlife areas.
-
B.
Marondera
Marondera is a town in eastern Zimbabwe known as an agricultural and educational center within the Mashonaland region.
-
C.
Kapiri Mposhi
Kapiri Mposhi is a town in central Zambia that serves as a key rail and road junction linking the country to Tanzania and other regions.
-
D.
Chegutu
Chegutu is a town in central northern Zimbabwe known for its agricultural activities and gold mining.
-
E.
Chinhoyi
Chinhoyi is a town in northern Zimbabwe known as an administrative center and for the nearby Chinhoyi Caves.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3577043048190bc9bcf55069b769f |
completed | April 18, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006edfe7f08190857fc6f66f3be9a0 |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:15 a.m.