Triple

T31398483
Position Surface form Disambiguated ID Type / Status
Subject Kaniguram dialect E800926 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Ormuri C60995 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 Ormuri
Context triple: [Kaniguram dialect, instanceOf, regional variety of Ormuri]
  • A. regional variety of Ghomalaʼ
    A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular area or community.
  • B. regional variety of Garhwali
    A regional variety of Garhwali is a localized form of the Garhwali language distinguished by its unique phonological, lexical, and syntactic features specific to a particular area within the Garhwal region.
  • C. regional variety of Burushaski
    A regional variety of Burushaski is a geographically distinct form of the Burushaski language characterized by localized differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Burushaski varieties.
  • 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. regional variety of Ghomalaʼ language
    A regional variety of the Ghomalaʼ language is a geographically or socially distinct form of Ghomalaʼ characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Ghomalaʼ varieties.
  • 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_69f224ea9998819086ae2e4f4f4091c8 completed April 29, 2026, 3:34 p.m.
Created at: April 29, 2026, 9:19 p.m.