Triple
T10111491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Church of Christ (Latter Day Saints) |
E218250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | leadership position in a religious organization |
C6232
|
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: leadership position in a religious organization Context triple: [President of the Church of Christ (Latter Day Saints), instanceOf, leadership position in a religious organization]
-
A.
Christian religious office
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.
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.
-
C.
religious leadership office
chosen
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.
-
D.
member of the clergy
A member of the clergy is an individual formally ordained or authorized by a religious tradition to lead worship, perform sacred rites, provide spiritual guidance, and represent the faith community.
-
E.
clergy role
A clergy role represents an authorized religious position responsible for leading worship, providing spiritual guidance, and performing sacred rituals within a faith community.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.