Triple
T5769088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convocations and Church Assembly system |
E127282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representative church governance system |
C8559
|
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: representative church governance system Context triple: [Convocations and Church Assembly system, instanceOf, representative church governance system]
-
A.
form of church polity
chosen
A form of church polity is a specific organizational structure and system of governance that defines how authority, decision-making, and leadership are distributed and exercised within a Christian church or denomination.
-
B.
form of church polity
A form of church polity is a conceptual structure that defines how authority, decision-making, and governance are organized and exercised within a Christian church or denomination.
-
C.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
-
D.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
E.
state church
A state church is a religious organization officially endorsed and supported by a government, often enjoying special legal status and influence in public affairs.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.