Triple

T7671698
Position Surface form Disambiguated ID Type / Status
Subject Tibeto-Burman languages E173762 entity
Predicate includesLanguage P2177 FINISHED
Object Lisu E197137 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: Lisu | Statement: [Tibeto-Burman languages, includesLanguage, Lisu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lisu
Context triple: [Tibeto-Burman languages, includesLanguage, Lisu]
  • A. Lisu chosen
    The Lisu are an ethnic minority people of the mountainous regions of southwest China and neighboring countries, known for their distinct Tibeto-Burman language, traditional music, and vibrant festivals.
  • B. Dholuo
    Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
  • C. Siwu language
    The Siwu language is a Niger-Congo language spoken primarily in the Volta Region of Ghana by the Mawu people.
  • D. Jingpo language
    The Jingpo language is a Tibeto-Burman language spoken primarily by the Jingpo (Kachin) people in northern Myanmar and adjacent regions of China and India.
  • E. Chochenyo
    Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
  • 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_69c699562484819086752091e3164a27 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c701dd3c808190990e07ced94b3297 completed March 27, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a229dd348190b9a781b4d34d7b5b completed March 29, 2026, 3:53 a.m.
Created at: March 27, 2026, 4 p.m.