Triple
T20299301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junius Manuscript |
E505436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old English poetic codex |
C16965
|
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: Old English poetic codex Context triple: [Junius Manuscript, instanceOf, Old English poetic codex]
-
A.
Old English poetry manuscript
chosen
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.
-
B.
Old English manuscript
An Old English manuscript is a handwritten document from early medieval England, typically on parchment, preserving texts in the Old English language along with their contemporary script, ornamentation, and material features.
-
C.
Anglo-Saxon literary collection
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.
-
D.
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.
-
E.
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.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:16 a.m.