Triple

T4302708
Position Surface form Disambiguated ID Type / Status
Subject Oshiwambo E99877 entity
Predicate hasDialect P4251 FINISHED
Object Oshindonga E143250 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: Oshindonga | Statement: [Oshiwambo, hasDialect, Oshindonga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oshindonga
Context triple: [Oshiwambo, hasDialect, Oshindonga]
  • A. Ongwediva
    Ongwediva is a growing town in northern Namibia known as an educational and commercial hub, hosting institutions like the University of Namibia’s campus and the annual Ongwediva Trade Fair.
  • B. Ondangwa
    Ondangwa is a town in northern Namibia that serves as an important commercial and transport hub for the surrounding Oshana Region.
  • C. Omaruru
    Omaruru is a small historic town in central Namibia known for its colonial-era architecture, vineyards, and role as a local trading and farming center.
  • D. Ovambo chosen
    Ovambo is a Bantu language spoken primarily by the Ovambo people in northern Namibia and southern Angola.
  • E. Gokwe
    Gokwe is a town in central Zimbabwe known for its cotton farming and role as a commercial hub in the Midlands Province.
  • 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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b350b66450819089c9ff6ff9f045e5 completed March 12, 2026, 11:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c7507f1081909cf737dff00542d9 completed March 14, 2026, 8:38 p.m.
Created at: March 12, 2026, 11:08 p.m.