Triple
T8576669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe Plateau |
E203063
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kwekwe |
E385563
|
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: Kwekwe | Statement: [Zimbabwe Plateau, contains, Kwekwe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kwekwe Context triple: [Zimbabwe Plateau, contains, Kwekwe]
-
A.
Kwekwe
chosen
Kwekwe is an industrial and mining city in central Zimbabwe known for its steel production and gold mining activities.
-
B.
Kesbewa
Kesbewa is a suburban town in Sri Lanka’s Western Province, situated within the greater Colombo metropolitan area.
-
C.
Oshikwambi
Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
-
D.
Kukawa
Kukawa is a historic town in northeastern Nigeria that once served as the political and cultural center of the Kanuri people and the Bornu Empire.
-
E.
Kuvinga
Kuvinga is an alternative name for the Kuvi language, a Dravidian language spoken by indigenous communities in eastern India.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea97787481909ebbaa45f59cbdaa |
completed | March 31, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce899dd7d48190b44338b92ad68bd0 |
completed | April 2, 2026, 3:22 p.m. |
Created at: March 30, 2026, 6:21 p.m.