Triple
T22455902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catechisms in Old Prussian |
E555114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Prussian-language text |
C6283
|
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 Prussian-language text Context triple: [Catechisms in Old Prussian, instanceOf, Old Prussian-language text]
-
A.
Baltic German
A Baltic German is a member of the historically German-speaking minority that lived in the Baltic region (primarily present-day Estonia and Latvia), often forming part of the local urban elite and nobility from medieval times until the 20th century.
-
B.
Old Dutch text
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.
Baltic language
chosen
A Baltic language is a member of the Indo-European language family spoken primarily around the eastern coast of the Baltic Sea, characterized by conservative grammatical features and rich inflectional morphology.
-
D.
Old High German poem
An Old High German poem is a verse composition written in the Old High German language (c. 750–1050 CE), typically preserved in medieval manuscripts and reflecting early Germanic culture, Christianization, and poetic traditions.
-
E.
Gothic-language text
A Gothic-language text is any written work composed in the extinct East Germanic language Gothic, typically preserved in manuscripts such as biblical translations and legal or liturgical documents from the early medieval period.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.