Triple
T3558814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washo language |
E75283
|
entity |
| Predicate | hasVoicelessVowels |
P18452
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Washo language, hasVoicelessVowels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoicelessVowels Context triple: [Washo language, hasVoicelessVowels, yes]
-
A.
hasNasalVowels
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
-
B.
hasVowelSystem
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
-
C.
hasPhonemicVowels
Indicates that a language or linguistic system distinguishes vowel sounds as separate phonemes that can change word meaning.
-
D.
hasVowelFeature
chosen
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
-
E.
hasEjectiveConsonants
Indicates that a language’s consonant inventory includes ejective consonants, produced with a glottalic egressive airstream mechanism.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0881d50819092332491b9527c9d |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.