Triple
T9011365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukpa language |
E215479
|
entity |
| Predicate | hasPhonemicNasalVowels |
P7439
|
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: [Yukpa language, hasPhonemicNasalVowels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonemicNasalVowels Context triple: [Yukpa language, hasPhonemicNasalVowels, true]
-
A.
hasNasalVowels
chosen
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
-
B.
hasPhonemicVowels
Indicates that a language or linguistic system distinguishes vowel sounds as separate phonemes that can change word meaning.
-
C.
hasNasalConsonants
Indicates that the subject language or word includes one or more nasal consonant sounds in its phonological inventory or pronunciation.
-
D.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
E.
hasPhonemicContrast
Indicates that two or more speech sounds are distinguished in a language by differences that change word meaning.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c1571881908d0b144786b5ee1f |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:06 p.m.