Triple
T10113288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Spiritual Assembly |
E218294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local religious governing council |
C17659
|
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: local religious governing council Context triple: [Local Spiritual Assembly, instanceOf, local religious governing council]
-
A.
religious organization board
chosen
A religious organization board is a governing body of appointed or elected individuals responsible for overseeing the spiritual, administrative, financial, and strategic direction of a faith-based institution.
-
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.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
D.
department of a religious denomination
A department of a religious denomination is an organizational unit within the denomination responsible for overseeing and coordinating specific functions, ministries, or areas of work such as education, missions, finance, or social services.
-
E.
religious league
A religious league is an organized alliance of states, groups, or individuals united primarily by shared religious beliefs or interests to pursue common political, military, or social goals.
- 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:04 p.m.