Triple
T28728071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus Bodmer XIII |
E730280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patristic manuscript |
C2085
|
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: patristic manuscript Context triple: [Papyrus Bodmer XIII, instanceOf, patristic manuscript]
-
A.
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.
-
B.
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.
-
C.
Vetus Latina manuscript
A Vetus Latina manuscript is a handwritten document preserving an Old Latin (pre-Vulgate) translation of biblical texts used in the Western Church before Jerome’s standardized Vulgate.
-
D.
ancient manuscripts
chosen
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.
-
E.
patristic text
A patristic text is a written work authored by an early Christian theologian or Church Father, typically from the first to eighth centuries, that contributes to the development of Christian doctrine, exegesis, and pastoral teaching.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:56 a.m.