Triple
T15149482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuscript Wormianus |
E361898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Norse manuscript |
C36032
|
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 Norse manuscript Context triple: [Manuscript Wormianus, instanceOf, Old Norse manuscript]
-
A.
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.
-
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.
Glagolitic manuscript
A Glagolitic manuscript is a handwritten document produced using the Glagolitic alphabet, one of the earliest Slavic scripts, typically preserving religious, liturgical, or legal texts from the medieval Slavic cultural sphere.
-
D.
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.
-
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. 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.