Triple
T18312099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oshindonga |
E438652
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Central Oshindonga |
—
|
NE NERFINISHED |
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: Central Oshindonga | Statement: [Oshindonga, hasDialects, Central Oshindonga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Central Oshindonga Context triple: [Oshindonga, hasDialects, Central Oshindonga]
-
A.
Oshindonga
chosen
Oshindonga is a standardized Bantu language variety spoken primarily in northern Namibia and southern Angola, forming one of the main dialects of the Oshiwambo language cluster.
-
B.
Ogwa
Ogwa is a town located within Aniocha South Local Government Area in Delta State, southern Nigeria.
-
C.
Oglewu
Oglewu is a town in Ohimini Local Government Area of Benue State, Nigeria.
-
D.
Ogwashi-Uku
Ogwashi-Uku is a prominent town in Delta State, Nigeria, known as one of the key urban centers of the Anioma (Igbo-speaking) area.
-
E.
Odzi River
The Odzi River is a significant river in eastern Zimbabwe that flows through Manicaland Province and contributes to the Save River system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50219cd548190b8da5f402d5da773 |
completed | April 19, 2026, 4:26 p.m. |
Created at: April 10, 2026, 10:36 a.m.