Triple
T7568030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Mercia |
E178969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon diocese |
C18560
|
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 diocese Context triple: [Diocese of Mercia, instanceOf, Anglo-Saxon diocese]
-
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.
former Church of England diocese
chosen
A former Church of England diocese is an ecclesiastical jurisdiction that once functioned as an administrative and pastoral district under a bishop within the Church of England but has since been dissolved, merged, or otherwise reorganized.
-
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.
medieval Scottish bishopric
A medieval Scottish bishopric was an ecclesiastical jurisdiction headed by a bishop, overseeing the spiritual, administrative, and often political affairs of the Church within a defined region of Scotland during the Middle Ages.
-
E.
late Roman diocese
A late Roman diocese was a large administrative district of the Roman Empire, grouping several provinces under the authority of a vicarius to improve governance, taxation, and imperial control.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:51 p.m.