Triple
T21118279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Vercellensis |
E520355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin manuscript |
C24468
|
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: Latin manuscript Context triple: [Codex Vercellensis, instanceOf, Latin manuscript]
-
A.
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.
-
B.
late antique manuscript
chosen
A late antique manuscript is a handwritten document produced between roughly the 3rd and 8th centuries CE, typically on papyrus or parchment, reflecting the transitional cultural, religious, and artistic practices of the late Roman and early medieval worlds.
-
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.
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.
-
E.
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.
- 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.