Triple

T26047382
Position Surface form Disambiguated ID Type / Status
Subject Iranun of Mindanao E647871 entity
Predicate instanceOf P0 FINISHED
Object variety of the Iranun language C50178 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: variety of the Iranun language
Context triple: [Iranun of Mindanao, instanceOf, variety of the Iranun language]
  • A. variety of the Isnag language
    A variety of the Isnag language is a regional or social form of Isnag distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
  • B. variety of Gorani language
    A variety of Gorani language is a regional or social form of the Gorani speech continuum, distinguished by its own phonological, lexical, and grammatical features while remaining mutually intelligible with other Gorani varieties.
  • C. 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.
  • D. variety of Tabasaran language
    A variety of the Tabasaran language is a regional or social form of Tabasaran distinguished by systematic differences in pronunciation, vocabulary, or grammar within the broader Tabasaran linguistic continuum.
  • E. variety of Avar language
    A variety of Avar language is a regional or social form of the Avar language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Avar forms.
  • 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_69e77e8d419481908004e6318d28aaab completed April 21, 2026, 1:41 p.m.
Created at: April 22, 2026, 9:10 a.m.