Triple

T14424028
Position Surface form Disambiguated ID Type / Status
Subject Lolo-Burmese E357649 entity
Predicate hasMajorLanguage P207 FINISHED
Object Lahu language E1099226 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: Lahu language | Statement: [Lolo-Burmese, hasMajorLanguage, Lahu language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lahu language
Context triple: [Lolo-Burmese, hasMajorLanguage, Lahu language]
  • A. Lahu language chosen
    The Lahu language is a Tibeto-Burman language spoken primarily by the Lahu people in the border regions of China, Myanmar, Thailand, and Laos.
  • B. Laha language
    The Laha language is a lesser-known Kra language spoken by the Laha ethnic group in northern Vietnam.
  • C. Pa’O language
    The Pa’O language is a Tibeto-Burman language spoken primarily by the Pa’O (Taungthu) people of Myanmar, especially in Shan and Kayin States.
  • D. A-Hmao language
    The A-Hmao language is a Hmong-Mien language spoken primarily by the A-Hmao subgroup of the Miao people in southwestern China.
  • E. Achuar-Shiwiar language
    The Achuar-Shiwiar language is a Jivaroan language spoken by the Achuar and Shiwiar Indigenous peoples of the Amazon rainforest in Ecuador and Peru.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91123f848190ba3fb18a76c2d24c completed April 14, 2026, 7:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd64898c088190ab4eef32ca4f5ed6 completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:18 a.m.