Triple
T37820487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Dutch Arthurian romances |
E942899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Dutch literature |
C64713
|
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: Middle Dutch literature Context triple: [Middle Dutch Arthurian romances, instanceOf, Middle Dutch literature]
-
A.
Old Frisian literature
Old Frisian literature comprises the body of written texts in the Old Frisian language, including legal codes, religious writings, and poetic fragments produced between roughly the 13th and 16th centuries in the Frisian-speaking regions along the North Sea coast.
-
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.
medieval literary language
Medieval literary language is the stylized, often highly formal written register of Middle Ages texts, shaped by manuscript culture, regional dialects, and genre-specific conventions distinct from everyday speech.
-
D.
North Germanic literature
North Germanic literature encompasses the written and oral literary traditions produced in the North Germanic languages (such as Old Norse, Icelandic, Norwegian, Danish, and Swedish), from medieval sagas and eddas to modern prose and poetry.
-
E.
Middle High German text
A Middle High German text is a written work composed in the High German dialects used roughly between 1050 and 1350, reflecting the language, culture, and literary traditions of medieval German-speaking regions.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.