Triple
T23046616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Lindisfarne |
E573893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval ecclesiastical office |
C6233
|
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 ecclesiastical office Context triple: [Bishop of Lindisfarne, instanceOf, medieval ecclesiastical office]
-
A.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
-
B.
bishopric office
A bishopric office is an administrative and pastoral center where a bishop and their staff conduct the governance, coordination, and support of ecclesiastical activities within a diocese or similar church jurisdiction.
-
C.
office in the Catholic Church
chosen
An office in the Catholic Church is an established position of ecclesiastical responsibility, authority, or service, entrusted to a person for the governance, ministry, or administration of the Church.
-
D.
medieval clergyman
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.
-
E.
Anglican clerical position
An Anglican clerical position is an official role within the Anglican Church’s ordained or licensed ministry structure, encompassing responsibilities for worship, pastoral care, administration, and spiritual leadership in a parish or wider ecclesiastical jurisdiction.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:54 p.m.