Triple
T37684029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fundamentalist Church of Jesus Christ of Latter-Day Saints priesthood council |
E938315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | priesthood council |
C1457
|
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: priesthood council Context triple: [Fundamentalist Church of Jesus Christ of Latter-Day Saints priesthood council, instanceOf, priesthood council]
-
A.
priestly sodality
A priestly sodality is a structured association of clergy united by shared spiritual practices, mutual support, and a common commitment to specific religious ideals or ministries.
-
B.
Kirchliches Gremium
Ein kirchliches Gremium ist eine organisierte Gruppe von Personen innerhalb einer Kirche, die gemeinsam Entscheidungen trifft, Beratungsaufgaben wahrnimmt oder bestimmte Verantwortungsbereiche in der kirchlichen Leitung und Verwaltung ausübt.
-
C.
ecclesiastical council
chosen
An ecclesiastical council is a formal assembly of church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
D.
LDS Church priesthood office
An LDS Church priesthood office is a divinely authorized role within the priesthood hierarchy that grants specific spiritual authority, responsibilities, and duties to its holder.
-
E.
representative church council
A representative church council is a governing body composed of elected or appointed delegates from various congregations or church units that meets to deliberate, decide, and provide guidance on matters of doctrine, policy, and administration for the wider church.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.