Triple
T6446645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet of Zimbabwe |
E138358
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Shona |
E28785
|
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: Shona | Statement: [Cabinet of Zimbabwe, language, Shona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shona Context triple: [Cabinet of Zimbabwe, language, Shona]
-
A.
Shona
chosen
Shona is a major Bantu language of Zimbabwe, widely spoken by the Shona people and used in education, media, and government.
-
B.
Tumbuka
Tumbuka is a Bantu language spoken primarily in northern Malawi and parts of Zambia and Tanzania.
-
C.
Tshivenda
Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
-
D.
Chichewa
Chichewa is a major Bantu language spoken primarily in Malawi and neighboring countries, serving as a national and widely used lingua franca in the region.
-
E.
Xitsonga
Xitsonga is a Bantu language spoken primarily by the Tsonga people in southern Africa, notably in South Africa, Mozambique, and Zimbabwe.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698edeac81909426902471d8a57b |
completed | March 22, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64bcd09e0819097eb60d13e8058dd |
completed | March 27, 2026, 9:20 a.m. |
Created at: March 22, 2026, 4:46 p.m.