Triple
T28781523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Supreme Church Council |
E726689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant church council |
C53601
|
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: Protestant church council Context triple: [Evangelical Supreme Church Council, instanceOf, Protestant church council]
-
A.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
-
B.
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.
-
C.
Protestant federation
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
-
D.
representative church council
chosen
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.
-
E.
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.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:19 a.m.