Triple

T6400256
Position Surface form Disambiguated ID Type / Status
Subject Ivasayen Ivatan E144043 entity
Predicate instanceOf P0 FINISHED
Object Ivatan language variety C20404 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: Ivatan language variety
Context triple: [Ivasayen Ivatan, instanceOf, Ivatan language variety]
  • A. Bikol language
    The Bikol language is an Austronesian language (or group of closely related languages) spoken primarily in the Bicol Region of the Philippines, known for its distinct phonology and vocabulary while sharing many features with other Central Philippine languages.
  • B. Nicobarese language variety
    A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
  • C. Yana language variety
    Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
  • D. Central Luzon language
    A Central Luzon language is a member of a subgroup of Philippine Austronesian languages spoken primarily in the Central Luzon region of the Philippines, characterized by shared phonological, grammatical, and lexical features distinct from other Philippine language groups.
  • E. Tai language
    A Tai language is a member of the Tai branch of the Kra–Dai language family, characterized by tonal phonology and analytic grammar, spoken primarily in Southeast Asia by Tai ethnic groups.
  • 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_69c008dc56fc81908d43ffcc11d73bdd completed March 22, 2026, 3:21 p.m.
Created at: March 22, 2026, 4:35 p.m.