Triple
T26005101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS. Mex. d. 1 |
E646734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bodleian Library manuscript |
C50435
|
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: Bodleian Library manuscript Context triple: [MS. Mex. d. 1, instanceOf, Bodleian Library manuscript]
-
A.
Gothic manuscript
A Gothic manuscript is a handwritten book or document produced in medieval Europe, characterized by dense, angular Gothic script, elaborate illumination, and often religious or legal content.
-
B.
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.
-
C.
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.
-
D.
Insular manuscript
An Insular manuscript is a handwritten book produced in the British Isles between the 7th and 9th centuries, characterized by distinctive Hiberno-Saxon script, intricate interlace ornament, and elaborate decorated initials.
-
E.
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.
- F. None of above. chosen
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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9 a.m.