Triple
T13959525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wachtendonck Psalms |
E335754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Dutch manuscript collection |
C12455
|
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: Old Dutch manuscript collection Context triple: [Wachtendonck Psalms, instanceOf, Old Dutch manuscript collection]
-
A.
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.
-
B.
Old Dutch text
chosen
Old Dutch text is a written representation of the early medieval West Germanic language spoken in the Low Countries between roughly the 6th and 12th centuries, preserved in manuscripts, glosses, and legal or religious documents.
-
C.
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.
-
D.
medieval Hebrew manuscript
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.
-
E.
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.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.