Triple
T37816629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Shift |
E942793
|
entity |
| Predicate | affectsVowel |
P54935
|
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: [Canadian Shift, affectsVowel, /æ/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsVowel Context triple: [Canadian Shift, affectsVowel, /æ/]
-
A.
effectOnVowelHeight
Indicates how one element influences the relative vertical tongue position (height) of a vowel in pronunciation.
-
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.
affectsPhonemeClass
chosen
Indicates that one element influences or changes the properties, behavior, or realization of a particular class of phonemes.
-
E.
isVowel
Indicates that the referenced character or symbol is a vowel in the relevant alphabet or phonetic system.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:19 p.m.