Triple

T26095979
Position Surface form Disambiguated ID Type / Status
Subject Rudraprayagi Garhwali E658266 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Garhwali C51109 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 Garhwali
Context triple: [Rudraprayagi Garhwali, instanceOf, regional variety of Garhwali]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. regional variety of Bengali
    A regional variety of Bengali is a localized form of the Bengali language characterized by distinct phonological, lexical, and sometimes grammatical features associated with a specific geographic area or speech community.
  • E. regional variety of Siwu language
    A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
  • 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_69ee5bbfc4d08190a1b206d0ac3a1e8d completed April 26, 2026, 6:38 p.m.
Created at: April 26, 2026, 7:51 p.m.