Triple
T28512233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary of the Holy Synod of the Assyrian Church of the East |
E721519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church administrative position |
C6971
|
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: church administrative position Context triple: [Secretary of the Holy Synod of the Assyrian Church of the East, instanceOf, church administrative position]
-
A.
Christian religious office
chosen
A Christian religious office is an institutional role or position within a Christian church or denomination, endowed with specific spiritual, liturgical, and administrative responsibilities and authority.
-
B.
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.
-
C.
head of church
The head of church is the highest-ranking religious leader who holds ultimate spiritual authority and administrative responsibility over a particular Christian church or denomination.
-
D.
parish official
A parish official is a person appointed or elected to manage the administrative, financial, and pastoral affairs of a local church parish or civil parish community.
-
E.
church order
Church order is the structured system of governance, rules, and practices that organizes the leadership, worship, discipline, and communal life of a Christian church or denomination.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:13 a.m.