Triple

T11912336
Position Surface form Disambiguated ID Type / Status
Subject Standard German phonology E283425 entity
Predicate hasDiphthong P102312 FINISHED
Object /aɪ/ 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: /aɪ/ | Statement: [Standard German phonology, hasDiphthong, /aɪ/]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDiphthong
Context triple: [Standard German phonology, hasDiphthong, /aɪ/]
  • A. 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.
  • B. hasGeminateConsonants
    Indicates that a word, morpheme, or phonological form contains one or more geminate (doubled or lengthened) consonant sounds.
  • 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. hasNasalVowels
    Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
  • E. hasVow
    Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
  • F. None of above. chosen

Provenance (4 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_69d6ab2c07e88190ba13b0d21fd6cf33 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e528f6748190ac873a040a61fa93 completed April 10, 2026, 11:55 a.m.
PD Predicate disambiguation batch_69d8bb3632ac8190b13e53c2b5db7125 completed April 10, 2026, 8:56 a.m.
PDg Predicate description generation batch_69d8dd0ba0f88190b7d5e358c27ca184 completed April 10, 2026, 11:20 a.m.
Created at: April 8, 2026, 9:44 p.m.