Triple

T16710728
Position Surface form Disambiguated ID Type / Status
Subject Awankari E406099 entity
Predicate instanceOf P0 FINISHED
Object Northwestern Indo-Aryan language C33096 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: Northwestern Indo-Aryan language
Context triple: [Awankari, instanceOf, Northwestern Indo-Aryan language]
  • A. Dardic language chosen
    A Dardic language is a member of a subgroup of the Indo-Aryan languages spoken primarily in the mountainous regions of northern Pakistan, northwestern India, and eastern Afghanistan, characterized by distinct phonological and lexical features.
  • B. Dravidian language
    A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
  • C. Indo-Aryan language variety
    An Indo-Aryan language variety is a specific form or dialect of a language within the Indo-Aryan branch of the Indo-European family, characterized by shared historical origins and linguistic features such as phonology, grammar, and vocabulary.
  • D. Bihari languages
    Bihari languages are a group of closely related Indo-Aryan languages and dialects spoken primarily in the Indian state of Bihar and surrounding regions, including Bhojpuri, Maithili, and Magahi.
  • E. Northwest Iranian language
    A Northwest Iranian language is a member of the western branch of the Iranian languages spoken primarily in regions of northwestern Iran and neighboring areas, characterized by shared phonological, lexical, and grammatical features distinct from Southwest Iranian languages.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
Created at: April 10, 2026, 5:20 a.m.