Triple
T19980183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth and Bargy dialect |
E493796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle English dialect |
C1327
|
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: Middle English dialect Context triple: [Forth and Bargy dialect, instanceOf, Middle English dialect]
-
A.
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.
-
B.
group of English dialects
chosen
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.
-
C.
Middle English manuscript
A Middle English manuscript is a handwritten document produced between the late 11th and late 15th centuries in the Middle English language, often preserving literary, religious, legal, or administrative texts in their original medieval form.
-
D.
Old English term
An Old English term is a word or expression originating from the early medieval English language (circa 5th–11th centuries), often preserved in historical texts and studied for its linguistic and cultural significance.
-
E.
Middle English author
A Middle English author is a writer who composed literary, religious, or historical works in the Middle English language, primarily between the late 11th and late 15th centuries in England.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:27 p.m.