Triple
T8475737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Argenteus |
E200388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic manuscript |
C24467
|
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: Gothic manuscript Context triple: [Codex Argenteus, instanceOf, Gothic manuscript]
-
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.
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.
-
C.
Gospel book
A Gospel book is a handwritten or printed volume containing the text of one or more of the four canonical Christian Gospels, often richly decorated and used in liturgy and devotion.
-
D.
Anglo-Norman manuscript tradition
The Anglo-Norman manuscript tradition encompasses the body of texts written in Anglo-Norman French in medieval England, preserved and transmitted through manuscripts that reflect the linguistic, cultural, and political interplay between Norman and English societies from the 11th to the 15th centuries.
-
E.
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.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:12 p.m.