Triple

T32847176
Position Surface form Disambiguated ID Type / Status
Subject Wessobrunn Prayer E840129 entity
Predicate instanceOf P0 FINISHED
Object Old High German poetic text C5472 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 High German poetic text
Context triple: [Wessobrunn Prayer, instanceOf, Old High German poetic text]
  • A. Old High German poem chosen
    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.
  • B. 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.
  • C. Middle High German poet
    A Middle High German poet is a literary figure who composed verse in the Middle High German language, typically between the 11th and 14th centuries, often focusing on themes such as courtly love, chivalry, and religious devotion.
  • D. manuscript containing Old High German text
    A manuscript containing Old High German text is a handwritten document, typically from the early Middle Ages, that preserves linguistic, literary, or religious material in the Old High German language.
  • E. 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.
  • 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_69f349412c78819084459850e11d29f7 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:17 a.m.