Triple
T23704472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberian codices |
E585680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval manuscripts |
C28376
|
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: medieval manuscripts Context triple: [Tiberian codices, instanceOf, medieval manuscripts]
-
A.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
B.
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.
-
C.
medieval Hebrew manuscript
chosen
A medieval Hebrew manuscript is a handwritten document produced between the 9th and 15th centuries in Hebrew script, often containing religious, legal, philosophical, or literary texts and frequently adorned with distinctive marginalia, illuminations, and scribal annotations.
-
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.
late antique manuscript
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.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:53 p.m.