Triple
T3094412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Cape Town |
E64558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian religious leadership 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: Christian religious leadership position Context triple: [Archbishop of Cape Town, instanceOf, Christian religious leadership 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.
Christian religious institution
A Christian religious institution is an organized body, such as a church or denomination, that structures, practices, and governs the communal worship, doctrine, and spiritual life of Christians.
-
D.
collective religious leadership
A collective religious leadership is a group of individuals who jointly hold and exercise spiritual, doctrinal, and organizational authority within a faith community.
-
E.
religious leadership office
A religious leadership office is an organizational unit or position within a faith community responsible for guiding spiritual practice, administering religious functions, and overseeing the governance and pastoral care of its members.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.