Triple

T7866965
Position Surface form Disambiguated ID Type / Status
Subject Nyamwezi people E182640 entity
Predicate language P15 FINISHED
Object Nyamwezi language E177048 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: Nyamwezi language | Statement: [Nyamwezi people, language, Nyamwezi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nyamwezi language
Context triple: [Nyamwezi people, language, Nyamwezi language]
  • A. Nyamwezi language chosen
    The Nyamwezi language is a Bantu language spoken primarily by the Nyamwezi people of western-central Tanzania.
  • B. Kinyankole language
    The Kinyankole language is a Bantu language spoken primarily by the Banyankole people in southwestern Uganda.
  • C. Sukuma–Nyamwezi languages
    The Sukuma–Nyamwezi languages are a closely related group of Bantu languages spoken primarily in northwestern Tanzania by the Sukuma, Nyamwezi, and neighboring ethnic groups.
  • D. Ngindo language
    The Ngindo language is a Bantu language spoken by the Ngindo people of southeastern Tanzania.
  • E. Nyaturu language
    The Nyaturu language is a Bantu language spoken primarily by the Nyaturu people in central Tanzania.
  • 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_69ca82894d9081908a832bfce71a4714 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb38464274819080f182b53783fa84 completed March 31, 2026, 2:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc5615a38c8190b11af9fe5b2e1422 completed March 31, 2026, 11:17 p.m.
Created at: March 30, 2026, 4:54 p.m.