Triple

T1023091
Position Surface form Disambiguated ID Type / Status
Subject Brahmi script E22081 entity
Predicate hasVowelNotation P16504 FINISHED
Object inherent vowel 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: inherent vowel | Statement: [Brahmi script, hasVowelNotation, inherent vowel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVowelNotation
Context triple: [Brahmi script, hasVowelNotation, inherent vowel]
  • A. hasVowelNotationSystem
    Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
  • B. hasVowelFeature
    Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
  • C. hasVowelHarmony
    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.
  • D. hasNasalVowels
    Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
  • E. hasDependentVowels chosen
    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.
  • 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_69a493d6e380819097b384986ffc315c completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b7e0f8908190bfe0a4cd8b31dfed completed March 1, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69a4b72619cc8190932fdfa0c74dc055 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:41 p.m.