Triple

T24245437
Position Surface form Disambiguated ID Type / Status
Subject Northern Rarámuri E603353 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Rarámuri C48231 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: regional variety of Rarámuri
Context triple: [Northern Rarámuri, instanceOf, regional variety of Rarámuri]
  • A. Rarámuri language variety chosen
    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.
  • B. Kaqchikel language variety
    The Kaqchikel language variety is a Mayan language spoken primarily in the central highlands of Guatemala, characterized by its agglutinative morphology, ergative-absolutive alignment, and rich system of aspect and status markers.
  • C. Mazatec language variety
    A Mazatec language variety is a specific regional or social form of the Mazatec language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazatecan linguistic continuum.
  • D. regional variety of Southern Tepehuán
    A regional variety of Southern Tepehuán is a geographically distinct form of the Southern Tepehuán language characterized by unique phonological, lexical, and grammatical features specific to a particular area or community.
  • E. regional variety of Guna language
    A regional variety of the Guna language is a geographically or socially distinct form of Guna characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Guna varieties.
  • F. None of above.

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_69e2953f631c819097cbb421046bd417 completed April 17, 2026, 8:17 p.m.
Created at: April 18, 2026, 12:04 a.m.