Triple
T19837429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | committees of the United States Conference of Catholic Bishops |
E476634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical committee structure |
C34267
|
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: ecclesiastical committee structure Context triple: [committees of the United States Conference of Catholic Bishops, instanceOf, ecclesiastical committee structure]
-
A.
ecclesiastical council
An ecclesiastical council is a formal assembly of church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
B.
theological commission
A theological commission is a formally appointed group of experts tasked with studying, evaluating, and advising on doctrinal, moral, or ecclesial questions within a religious tradition.
-
C.
religious organization committee
chosen
A religious organization committee is a structured group within a faith-based institution responsible for planning, coordinating, and overseeing specific religious, administrative, or community activities in alignment with the organization’s beliefs and goals.
-
D.
Catholic Church council
A Catholic Church council is a formal assembly of bishops and other church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
E.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.