Triple
T28207548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South English Legendary |
E717072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle English legendary |
C10607
|
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 legendary Context triple: [South English Legendary, instanceOf, Middle English legendary]
-
A.
Middle English narrative poem
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Old English literary work
An Old English literary work is a written composition created in the Old English language (c. 5th–11th centuries), encompassing genres such as poetry, prose, and religious or historical texts that reflect the culture and society of early medieval England.
-
E.
early medieval English person
An early medieval English person is an individual who lived in England roughly between the 5th and 11th centuries, shaped by a mix of Anglo-Saxon, Viking, and early Christian cultural, social, and political influences.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:36 p.m.