Triple

T9269151
Position Surface form Disambiguated ID Type / Status
Subject Karekare E222777 entity
Predicate hasNeighboringLanguage P16383 FINISHED
Object Ngamo E225046 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: Ngamo | Statement: [Karekare, hasNeighboringLanguage, Ngamo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ngamo
Context triple: [Karekare, hasNeighboringLanguage, Ngamo]
  • A. Ngamo chosen
    Ngamo is a West Chadic language spoken primarily in northeastern Nigeria by the Ngamo people.
  • B. Bagamoyo
    Bagamoyo is a historic coastal town in present-day Tanzania that served as a major 19th-century East African trade and colonial center, including as an early administrative hub for German rule.
  • C. Oshikwambi
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • D. Oshikwanyama
    Oshikwanyama is a Bantu language variety spoken primarily in northern Namibia and southern Angola, recognized as one of the major dialects of Oshiwambo.
  • E. Nyambo
    Nyambo are a Bantu-speaking ethnic group primarily inhabiting Tanzania’s Kagera Region near the western shores of Lake Victoria.
  • 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_69ca841ffe208190aa7bcffbef2f8379 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd074ef7408190b213c09491918132 completed April 1, 2026, 11:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0f38567048190b1fccbab145285c9 completed April 4, 2026, 11:18 a.m.
Created at: March 30, 2026, 7:33 p.m.