Triple
T3023957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Cities Vowel Shift region English |
E82531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Midwestern English dialect |
C1503
|
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: Midwestern English dialect Context triple: [Northern Cities Vowel Shift region English, instanceOf, Midwestern English dialect]
-
A.
group of English dialects
A group of English dialects is a collection of regionally or socially distinct varieties of the English language that share common linguistic features while differing in pronunciation, vocabulary, and grammar from other such groups.
-
B.
variety of American English
chosen
A variety of American English is a distinct, systematically patterned form of English used in the United States, characterized by particular phonological, lexical, grammatical, and pragmatic features associated with specific regions, social groups, or contexts.
-
C.
regional variety of Indian English
A regional variety of Indian English is a localized form of English spoken in a specific part of India, shaped by the region’s native languages, cultural norms, and pronunciation patterns.
-
D.
national variety of English
A national variety of English is a distinct form of the English language associated with a particular country, characterized by its own norms of pronunciation, vocabulary, grammar, and usage.
-
E.
coastal dialect
A coastal dialect is a regional variety of a language spoken in coastal areas, shaped by maritime culture, trade contact, and geographic isolation or connectivity along the shoreline.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.