Triple
T16039703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaonde people |
E389060
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | BaKaonde |
E344446
|
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: BaKaonde | Statement: [Kaonde people, ethnonym, BaKaonde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BaKaonde Context triple: [Kaonde people, ethnonym, BaKaonde]
-
A.
Kaonde
chosen
Kaonde is a Bantu language spoken primarily by the Kaonde people of northwestern Zambia and parts of the Democratic Republic of the Congo.
-
B.
Kibondo
Kibondo is a town in western Tanzania that serves as an administrative and commercial center in the Kigoma Region.
-
C.
Nakonde
Nakonde is a town in northeastern Zambia near the border with Tanzania, serving as a key border crossing and trade hub between the two countries.
-
D.
Bongwe
Bongwe is a dialect of the Duala language spoken by the Duala people of Cameroon.
-
E.
Oshikwambi
Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833f84188190baa3a452df880284 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd77c5481908644742a8a8f3e68 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.