Triple

T36631664
Position Surface form Disambiguated ID Type / Status
Subject Miza E904336 entity
Predicate instanceOf P0 FINISHED
Object Moru language variety C63832 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: Moru language variety
Context triple: [Miza, instanceOf, Moru language variety]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. Kunama language variety
    A Kunama language variety is a specific regional or social form of the Kunama language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Kunama linguistic continuum.
  • E. Aja language variety
    Aja language variety refers to any of the regional or social forms of the Aja language, a Gbe language spoken primarily in Benin and Togo, distinguished by differences in pronunciation, vocabulary, and grammar.
  • 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_69f76e6c63e48190b1d0c3a79a6c7406 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:11 p.m.