Triple
T8524508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Lichfield |
E201777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval English church office |
C7027
|
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 English church office Context triple: [Archbishop of Lichfield, instanceOf, medieval English church office]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Anglican cleric
An Anglican cleric is an ordained minister in the Anglican tradition who leads worship, administers sacraments, provides pastoral care, and upholds the doctrine and discipline of the Anglican Church.
-
E.
organ of the Church of England
chosen
An organ of the Church of England is a formal body or instrument—such as a synod, bishop, or ecclesiastical court—through which the Church carries out its governance, decision-making, and official functions.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:16 p.m.