Triple

T6366921
Position Surface form Disambiguated ID Type / Status
Subject Ovambo E143250 entity
Predicate hasDialect P4251 FINISHED
Object Aakwambi E435319 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: Aakwambi | Statement: [Ovambo, hasDialect, Aakwambi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aakwambi
Context triple: [Ovambo, hasDialect, Aakwambi]
  • A. Akwanga
    Akwanga is a town and administrative center in central Nigeria known for its role as a commercial and educational hub in Nasarawa State.
  • B. Oshikwambi chosen
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • C. Ekwensu
    Ekwensu is a deity in the Odinani traditional religion of the Igbo people, often associated with war, negotiation, and trickery.
  • D. Akwamu
    Akwamu was a powerful early modern West African kingdom of the Akan people, known for its military expansion and control of key trade routes in what is now Ghana.
  • E. Eyamba
    Eyamba is a prominent clan of the Efik people of southeastern Nigeria, historically associated with leadership and influence in the Old Calabar region.
  • 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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06811de2881909ead116117956981 completed March 22, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640b2915481909f3251f9c34e8db2 completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:32 p.m.