Triple

T5882098
Position Surface form Disambiguated ID Type / Status
Subject Mishar Tatar E130771 entity
Predicate usesVowelHarmony P15727 FINISHED
Object true LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Mishar Tatar, usesVowelHarmony, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesVowelHarmony
Context triple: [Mishar Tatar, usesVowelHarmony, true]
  • A. hasVowelHarmony chosen
    Indicates that the phonological vowels in a word or morpheme conform to a systematic harmony pattern (e.g., all front or all back vowels) according to the language’s vowel harmony rules.
  • B. hasConsonantHarmony
    Indicates that the entities are related by a pattern where consonants within a linguistic unit adjust to share similar features, creating consonant harmony.
  • C. hasVowelSystem
    Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
  • D. hasNasalVowels
    Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
  • E. hasVowelNotationSystem
    Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
  • F. None of above.

Provenance (3 batches)

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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03fe07b7081909f8577ec3a9a1a8d completed March 22, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69c0334bdc308190ad0d7199ab975588 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 3:57 p.m.