Triple

T18758891
Position Surface form Disambiguated ID Type / Status
Subject Äynu language E458718 entity
Predicate instanceOf P0 FINISHED
Object Turkic–Iranian mixed language C41580 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: Turkic–Iranian mixed language
Context triple: [Äynu language, instanceOf, Turkic–Iranian mixed language]
  • A. Turkic language
    A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
  • B. 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.
  • C. Dardic language
    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.
  • D. branch of the Turkic languages
    A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
  • E. Northeast Caucasian language
    A Northeast Caucasian language is a member of a diverse family of languages spoken primarily in the northeastern Caucasus region, characterized by complex consonant systems and rich case morphology.
  • 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 11:52 a.m.