Triple
T34812187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ruling elders in the Presbyterian Church (USA) |
E1003527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lay ecclesiastical office |
C31886
|
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: lay ecclesiastical office Context triple: [ruling elders in the Presbyterian Church (USA), instanceOf, lay ecclesiastical office]
-
A.
archiepiscopal office
An archiepiscopal office is the official position, authority, and administrative center associated with an archbishop’s leadership over an archdiocese and its ecclesiastical affairs.
-
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.
Byzantine ecclesiastical office
A Byzantine ecclesiastical office is a formal clerical position within the hierarchical structure of the Eastern Roman (Byzantine) Church, encompassing specific liturgical, administrative, and judicial duties tied to the empire’s religious and imperial governance.
-
D.
lay cleric
chosen
A lay cleric is a devout non-ordained individual who performs certain religious or quasi-clerical duties within a faith community while remaining part of the laity.
-
E.
office in the Catholic Church
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.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.