Triple
T21118243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynewulfian canon |
E520354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of Old English religious poems |
C16966
|
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: group of Old English religious poems Context triple: [Cynewulfian canon, instanceOf, group of Old English religious poems]
-
A.
Old English homiletic collection
An Old English homiletic collection is a compiled set of sermons and religious teachings written in Old English, intended for use in preaching, instruction, and devotional reading in early medieval England.
-
B.
Anglo-Saxon literary collection
chosen
An Anglo-Saxon literary collection is an organized compilation of texts, poems, homilies, and other writings produced in or about the Anglo-Saxon period, typically preserved in manuscript form for study and reference.
-
C.
Old Norse poetry collection
A curated anthology of poetic works composed in Old Norse, typically preserving skaldic and Eddic verse along with contextual notes on language, mythology, and culture.
-
D.
Old English poetry manuscript
An Old English poetry manuscript is a handwritten medieval document preserving poetic texts in the Old English language, often featuring alliterative verse, scribal annotations, and culturally significant themes from Anglo-Saxon England.
-
E.
Old English religious text
An Old English religious text is a written work composed in the Old English language that conveys Christian doctrines, biblical narratives, liturgical materials, or moral teachings for spiritual instruction and devotion in early medieval 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:55 p.m.