Triple
T12276083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle English vowel system |
E292592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Middle English phonology |
C10521
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: component of Middle English phonology Context triple: [Middle English vowel system, instanceOf, component of Middle English phonology]
-
A.
phonological change
Phonological change is the systematic alteration of a language’s sound patterns over time, affecting how words are pronounced and sometimes how they are represented in writing.
-
B.
phonological system
chosen
A phonological system is the organized set of sounds and sound patterns in a language, along with the rules governing their combination and pronunciation.
-
C.
historical sound change
Historical sound change is the systematic alteration of speech sounds in a language over time, resulting in predictable shifts in pronunciation patterns across generations.
-
D.
Norman dialect
Norman dialect is a variety of the Romance language Norman, historically spoken in the region of Normandy and its surrounding areas, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard French.
-
E.
medieval North Germanic language variety
A medieval North Germanic language variety is a historical form of a Scandinavian language spoken in Northern Europe during the Middle Ages, characterized by its distinct phonology, morphology, and vocabulary relative to both earlier Norse and later modern Scandinavian languages.
- F. None of above.
Provenance (1 batch)
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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.