Triple

T1529118
Position Surface form Disambiguated ID Type / Status
Subject Eastern Nagari script E32400 entity
Predicate hasInherentVowel P16118 FINISHED
Object /ɔ/ 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: /ɔ/ | Statement: [Eastern Nagari script, hasInherentVowel, /ɔ/]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInherentVowel
Context triple: [Eastern Nagari script, hasInherentVowel, /ɔ/]
  • A. hasVowelFeature
    Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
  • B. defaultInherentVowel chosen
    Indicates that a writing system or script implicitly includes a specific vowel sound in a consonant symbol unless it is explicitly modified or suppressed.
  • C. hasDependentVowels
    Indicates that a writing system or script uses vowel signs that are attached to or depend on consonant characters rather than standing alone as independent letters.
  • D. hasIndependentVowelLetters
    Indicates that a writing system includes separate, standalone vowel characters rather than representing vowels only through modifications of consonant letters.
  • E. hasVowelSystem
    Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
  • 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_69a885ea86308190998f6bc14bb91f8e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a933ddc5a881909cdf503f2bc29bd4 completed March 5, 2026, 7:42 a.m.
PD Predicate disambiguation batch_69a907ae8f688190ad9000ea1e018585 completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.