Triple
T31139632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDS Church leadership |
E793745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious leadership structure |
C3006
|
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: religious leadership structure Context triple: [LDS Church leadership, instanceOf, religious leadership structure]
-
A.
collective religious leadership
chosen
A collective religious leadership is a group of individuals who jointly hold and exercise spiritual, doctrinal, and organizational authority within a faith community.
-
B.
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.
-
C.
religious structure
A religious structure is a building or space specifically designed and used for worship, rituals, and other activities associated with a particular faith or spiritual tradition.
-
D.
religious leadership succession
Religious leadership succession is the process by which authority and office are transferred from one spiritual leader to another within a religious tradition, according to its doctrines, laws, and customs.
-
E.
religious network
A religious network is a structured system of individuals, groups, and institutions connected by shared beliefs, practices, and organizational ties that facilitate the spread and maintenance of a religious tradition.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:05 p.m.