Triple
T16687334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwando River |
E405496
|
entity |
| Predicate | languageVariant |
P5595
|
FINISHED |
| Object | Kwando |
E336259
|
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: Kwando | Statement: [Kwando River, languageVariant, Kwando]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kwando Context triple: [Kwando River, languageVariant, Kwando]
-
A.
Kwando
chosen
Kwando is a river in southern Africa that flows through Angola, Namibia, and Botswana, forming part of the region’s complex wetland and river system.
-
B.
Kwandi
Kwandi is a regional dialect of the Silozi language spoken by communities in parts of southern Africa.
-
C.
Kwaluudhi
Kwaluudhi is a dialect of the Ovambo language spoken by a specific Ovambo subgroup in northern Namibia.
-
D.
Zamdela
Zamdela is a township suburb of Sasolburg in South Africa, primarily serving as a residential area for workers in the nearby industrial and petrochemical complexes.
-
E.
Ngwenyama
Ngwenyama is the traditional Swazi royal title meaning "lion," used for the reigning king of Eswatini.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea63b7081908a055036172f9683 |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a45af7c8190bfe09dd0e0573573 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 10, 2026, 5:19 a.m.