Triple

T22082472
Position Surface form Disambiguated ID Type / Status
Subject Sawndip E545685 entity
Predicate usedFor P98 FINISHED
Object Bouyei language NE NERFINISHED

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: Bouyei language | Statement: [Sawndip, usedFor, Bouyei language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bouyei language
Context triple: [Sawndip, usedFor, Bouyei language]
  • A. Bouyei language chosen
    The Bouyei language is a Tai–Kadai language spoken primarily by the Bouyei ethnic group in southern China, especially in Guizhou Province.
  • B. Buyi language
    The Buyi language is a Tai–Kadai language spoken primarily by the Buyi ethnic group in Guizhou and neighboring regions of southern China.
  • C. Batui language
    The Batui language is an Austronesian language spoken in Central Sulawesi, Indonesia, and is part of the Saluan–Banggai subgroup.
  • D. Bafia language
    The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
  • E. Keiyo language
    The Keiyo language is a Southern Nilotic language spoken by the Keiyo people of Kenya’s Rift Valley, closely associated with and linguistically similar to other Kalenjin languages such as Kipsigis.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e3523488190badd54b5d580c00d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128b706288190945c0c37e5ff2756 completed April 28, 2026, 9:37 p.m.
Created at: April 16, 2026, 8:28 p.m.