Triple
T19882567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honorius of Canterbury |
E477815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon church leader |
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: Anglo-Saxon church leader Context triple: [Honorius of Canterbury, instanceOf, Anglo-Saxon church leader]
-
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-Saxon missionary
An Anglo-Saxon missionary is a Christian evangelist from early medieval England who traveled to foreign regions, particularly continental Europe, to convert local populations and establish or strengthen the Church.
-
C.
Anglo-Saxon saint
An Anglo-Saxon saint is a holy person from the early medieval English period, venerated for their exemplary Christian life, miracles, or martyrdom within the Anglo-Saxon cultural and religious context.
-
D.
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.
-
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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.