Triple
T4760036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chancery Standard |
E105677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Middle English |
C2257
|
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: variety of Middle English Context triple: [Chancery Standard, instanceOf, variety of Middle English]
-
A.
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.
-
B.
national variety of English
chosen
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.
-
C.
Middle English narrative poem
A Middle English narrative poem is a verse composition written in the Middle English language that tells a structured story, often involving adventure, romance, morality, or religious themes.
-
D.
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.
-
E.
variety of American English
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.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.