Triple

T6200338
Position Surface form Disambiguated ID Type / Status
Subject Kuki-Chin languages E138612 entity
Predicate hasMember P10 FINISHED
Object Mro-Khimi language E575838 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: Mro-Khimi language | Statement: [Kuki-Chin languages, hasMember, Mro-Khimi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mro-Khimi language
Context triple: [Kuki-Chin languages, hasMember, Mro-Khimi language]
  • A. Kamviri language
    The Kamviri language is a Nuristani language spoken primarily by the Kam people in parts of eastern Afghanistan and neighboring regions of Pakistan.
  • B. Khumi language chosen
    The Khumi language is a lesser-known Tibeto-Burman language spoken primarily by the Khumi people in parts of Myanmar and neighboring regions.
  • C. Murle language
    The Murle language is an Eastern Sudanic language spoken primarily by the Murle people of South Sudan.
  • D. Kaxabu language
    The Kaxabu language is an indigenous Formosan language of Taiwan spoken by the Kaxabu people and considered highly endangered.
  • E. Sanglechi language
    The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
  • 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_69c008acbea48190991c6b834bb45d65 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062547cd48190a2715537b961262e completed March 22, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69c20d96415c8190b0c5c7f9fd19f5be completed March 24, 2026, 4:05 a.m.
Created at: March 22, 2026, 4:20 p.m.