Triple

T12347820
Position Surface form Disambiguated ID Type / Status
Subject Saint Adalbert of Prague E294403 entity
Predicate instanceOf P0 FINISHED
Object 10th-century bishop C31332 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: 10th-century bishop
Context triple: [Saint Adalbert of Prague, instanceOf, 10th-century bishop]
  • A. Anglo-Saxon bishop
    An Anglo-Saxon bishop was a high-ranking ecclesiastical leader in early medieval England responsible for overseeing a diocese, administering sacraments, guiding clergy and laity, and often advising kings in both religious and political matters.
  • B. 10th-century monarch
    A 10th-century monarch is a sovereign ruler who held supreme political and often religious authority over a kingdom or empire during the years 901–1000 CE, navigating feudal structures, dynastic struggles, and regional power shifts of the early medieval period.
  • C. Frankish bishop
    A Frankish bishop was a high-ranking cleric in the Frankish kingdoms who oversaw Christian religious life, administered dioceses, and often played significant political and cultural roles in early medieval Europe.
  • D. 5th-century Italian bishop
    A 5th-century Italian bishop was a high-ranking Christian cleric in Italy responsible for overseeing a diocese, guiding religious practice, and engaging in theological and political affairs during the late Roman and early post-Roman period.
  • E. Anglo-Saxon abbot
    An Anglo-Saxon abbot was the head of a monastic community in early medieval England, overseeing its spiritual life, administration, landholdings, and relations with secular and ecclesiastical authorities.
  • 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_69d6ab6ccbec8190b09e2d357aa80064 completed April 8, 2026, 7:24 p.m.
Created at: April 8, 2026, 9:53 p.m.