Triple

T30412583
Position Surface form Disambiguated ID Type / Status
Subject Jamatia dialect E773659 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Kokborok C56468 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 Kokborok
Context triple: [Jamatia dialect, instanceOf, regional variety of Kokborok]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. regional variety of Odia
    A regional variety of Odia is a geographically localized form of the Odia language characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
  • 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_69f22490b8b48190ab10c886a8d58c89 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 8:05 p.m.