Triple
T19979473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oswald as Bishop of Worcester |
E493777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 10th-century English churchman |
C10208
|
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 English churchman Context triple: [Oswald as Bishop of Worcester, instanceOf, 10th-century English churchman]
-
A.
Anglo-Saxon bishop
chosen
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.
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.
-
C.
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.
-
D.
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.
-
E.
Anglo-Saxon monk
An Anglo-Saxon monk is a member of a Christian religious community in early medieval England, devoted to prayer, learning, manuscript production, and the observance of monastic rules.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:27 p.m.