Triple

T23904165
Position Surface form Disambiguated ID Type / Status
Subject Osbert de Lincoln E601138 entity
Predicate instanceOf P0 FINISHED
Object medieval English cleric C16868 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: medieval English cleric
Context triple: [Osbert de Lincoln, instanceOf, medieval English cleric]
  • A. Anglo-Norman cleric
    An Anglo-Norman cleric is a religious official of the medieval Christian Church in England or Normandy after the Norman Conquest, typically involved in ecclesiastical administration, pastoral care, and the transmission of Latin learning within an Anglo-Norman cultural context.
  • B. medieval clergyman chosen
    A medieval clergyman is a religious official of the Christian Church in the Middle Ages who performs spiritual duties, administers sacraments, and often serves as an educator and advisor within both religious and secular communities.
  • C. Norman cleric
    A Norman cleric is a medieval religious official from Normandy who combines ecclesiastical duties with the administrative, cultural, and often political interests of the Norman ruling elite.
  • D. 13th-century English bishop
    A 13th-century English bishop was a high-ranking cleric in medieval England responsible for overseeing a diocese’s spiritual life, administering church law and property, and often advising the king in both religious and political matters.
  • E. medieval Christian monk
    A medieval Christian monk is a religious man who lives in a monastic community under vows of poverty, chastity, and obedience, dedicating his life to prayer, work, and spiritual study within the Christian tradition.
  • 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_69e295364a488190bcac702e9bb7f764 completed April 17, 2026, 8:16 p.m.
Created at: April 17, 2026, 8:26 p.m.