Triple

T5400285
Position Surface form Disambiguated ID Type / Status
Subject The Wife’s Lament E120756 entity
Predicate instanceOf P0 FINISHED
Object Anglo-Saxon literature work C17550 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: Anglo-Saxon literature work
Context triple: [The Wife’s Lament, instanceOf, Anglo-Saxon literature work]
  • A. Old English literary work chosen
    An Old English literary work is a written composition created in the Old English language (c. 5th–11th centuries), encompassing genres such as poetry, prose, and religious or historical texts that reflect the culture and society of early medieval England.
  • B. Anglo-Saxon literary collection
    An Anglo-Saxon literary collection is an organized compilation of texts, poems, homilies, and other writings produced in or about the Anglo-Saxon period, typically preserved in manuscript form for study and reference.
  • C. Old English writer
    An Old English writer is an author who composed literary, religious, or historical texts in the Old English language during the early medieval period in England.
  • D. Old English religious text
    An Old English religious text is a written work composed in the Old English language that conveys Christian doctrines, biblical narratives, liturgical materials, or moral teachings for spiritual instruction and devotion in early medieval England.
  • E. Old English poetry manuscript
    An Old English poetry manuscript is a handwritten medieval document preserving poetic texts in the Old English language, often featuring alliterative verse, scribal annotations, and culturally significant themes from Anglo-Saxon England.
  • 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_69bd4637b92c8190b815b6443ae4b323 completed March 20, 2026, 1:06 p.m.
Created at: March 20, 2026, 2:04 p.m.