Triple
T35900678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palimpsest |
E1038343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | codicological object |
C63941
|
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: codicological object Context triple: [Palimpsest, instanceOf, codicological object]
-
A.
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.
-
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.
manuscript siglum
A manuscript siglum is a concise symbol or code used by scholars to uniquely identify and reference a specific manuscript within critical editions, catalogues, or academic discussions.
-
D.
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.
-
E.
manuscript catalogue
A manuscript catalogue is a systematically organized listing that describes and indexes individual manuscripts within a collection, typically including details such as authorship, date, provenance, physical characteristics, and content summaries.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.