Triple

T30770027
Position Surface form Disambiguated ID Type / Status
Subject Bo Luang Lawa language E783495 entity
Predicate instanceOf P0 FINISHED
Object Lawa language variety C58802 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Lawa language variety
Context triple: [Bo Luang Lawa language, instanceOf, Lawa language variety]
  • A. Mari language variety
    A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-speaking community.
  • B. Yana language variety
    Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
  • C. variety of Lau language
    A variety of Lau language is a distinct regional or social form of the Lau language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Lau forms.
  • D. Luri language variety
    A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
  • E. Rarámuri language variety
    A Rarámuri language variety is a specific regional or social form of the Rarámuri (Tarahumara) language, distinguished by its unique phonological, lexical, and grammatical features within the broader Rarámuri linguistic continuum.
  • F. None of above. chosen

Provenance (1 batch)

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_69f224b1519081908b9db003fd2073e0 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:40 p.m.