Triple
T15496882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odzi River |
E378841
|
entity |
| Predicate | hasLanguageOrigin |
P1754
|
FINISHED |
| Object | Shona language |
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 language | Statement: [Odzi River, hasLanguageOrigin, Shona language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shona language Context triple: [Odzi River, hasLanguageOrigin, Shona language]
-
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.
Silozi language
The Silozi language is a Bantu language spoken primarily by the Lozi people in western Zambia and surrounding regions.
-
C.
Tumbuka
Tumbuka is a Bantu language spoken primarily in northern Malawi and parts of Zambia and Tanzania.
-
D.
Tshivenda
Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
-
E.
Mambwe-Lungu language
The Mambwe-Lungu language is a Bantu language spoken primarily in parts of Zambia and Tanzania by the Mambwe and closely related Lungu communities.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faecd60819091eeaa56c9c8f67d |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3665769c8190be1af51a82a5e75f |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 10, 2026, 3:52 a.m.