Triple

T28199296
Position Surface form Disambiguated ID Type / Status
Subject Madridejos dialect E716831 entity
Predicate instanceOf P0 FINISHED
Object variety of Bantayanon language C26670 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 Bantayanon language
Context triple: [Madridejos dialect, instanceOf, variety of Bantayanon language]
  • A. variety of the Kalanguya language
    A variety of the Kalanguya language is a regional or social form of Kalanguya distinguished by unique phonological, lexical, or grammatical features used by a particular speech community.
  • B. variety of Cebuano language
    A variety of Cebuano language is a regional or social form of Cebuano distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
  • C. Palawano language variety
    A Palawano language variety is a specific regional or ethnolinguistic form of the Palawano Austronesian language spoken by distinct Palawano communities on the island of Palawan in the Philippines.
  • D. Visayan language variety chosen
    A Visayan language variety is a specific regional or social form of any language within the Visayan (Bisayan) subgroup of the Austronesian language family, characterized by distinct phonological, lexical, and grammatical features.
  • E. variety of the Aralle-Tabulahan language
    A variety of the Aralle-Tabulahan language is a distinct regional or social form of this Austronesian language, characterized by its own specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Aralle-Tabulahan varieties.
  • 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_69efd6b826908190857e6e7dad74ed93 completed April 27, 2026, 9:35 p.m.
Created at: April 27, 2026, 10:29 p.m.