Triple
T8330123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Laudianus (E 08) |
E195053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek-Latin diglot manuscript |
C12261
|
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: Greek-Latin diglot manuscript Context triple: [Codex Laudianus (E 08), instanceOf, Greek-Latin diglot manuscript]
-
A.
Greek-Latin diglot
chosen
A Greek-Latin diglot is a bilingual text or edition in which Greek and Latin appear together, typically in parallel columns or facing pages, to facilitate comparison and study of both languages.
-
B.
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.
-
C.
Septuagint manuscript
A Septuagint manuscript is a handwritten copy of the ancient Greek translation of the Hebrew Bible (and related texts), produced and transmitted by scribes in antiquity and the medieval period.
-
D.
Bavarian manuscript
A Bavarian manuscript is a handwritten document produced in the historical region of Bavaria, typically reflecting its local language, script traditions, and cultural or religious practices of the time.
-
E.
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.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.