Triple

T17208088
Position Surface form Disambiguated ID Type / Status
Subject Oshiwambo languages E417652 entity
Predicate hasDialect P4251 FINISHED
Object Oshingandjera E438652 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: Oshingandjera | Statement: [Oshiwambo languages, hasDialect, Oshingandjera]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oshingandjera
Context triple: [Oshiwambo languages, hasDialect, Oshingandjera]
  • A. Oshikwambi
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • B. Changamire
    Changamire was the royal title borne by the supreme rulers of the Rozvi Empire in what is now Zimbabwe.
  • C. 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.
  • D. Egingwah
    Egingwah was an Inuit hunter and guide who played a crucial role in early 20th-century Arctic exploration, including expeditions toward the North Pole.
  • E. Bongwe
    Bongwe is a dialect of the Duala language spoken by the Duala people of Cameroon.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dc283648190b2c1f957940024aa completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01793aec4c81908e64226986866389 completed May 11, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:38 a.m.