Triple
T26160913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Elmham |
E660107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon episcopal see |
C47830
|
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 episcopal see Context triple: [Bishop of Elmham, instanceOf, Anglo-Saxon episcopal see]
-
A.
Anglican episcopal see
An Anglican episcopal see is the geographical area of jurisdiction and the associated office of a bishop within the Anglican Communion.
-
B.
ancient Christian episcopal see
chosen
An ancient Christian episcopal see is a historical bishopric that served as the central ecclesiastical jurisdiction and seat of a bishop in the early Christian Church.
-
C.
medieval Christian bishopric
A medieval Christian bishopric is an ecclesiastical jurisdiction governed by a bishop, encompassing both the spiritual authority over clergy and laity and the temporal control of lands, revenues, and often political influence within a defined region.
-
D.
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.
-
E.
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.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
Created at: April 26, 2026, 8:30 p.m.