Triple
T34811916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Presbyterian Church (USA) |
E1003521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Presbyterian polity document |
C63070
|
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: Presbyterian polity document Context triple: [Constitution of the Presbyterian Church (USA), instanceOf, Presbyterian polity document]
-
A.
Presbyterian confession
A Presbyterian confession is a formal, written doctrinal statement that summarizes the core beliefs and theological positions of Presbyterian churches, serving as a subordinate standard under the authority of Scripture.
-
B.
Presbyterian organization
A Presbyterian organization is a structured body within the Reformed Christian tradition that operates under Presbyterian governance, typically overseen by elected elders and organized into councils such as sessions, presbyteries, synods, and a general assembly.
-
C.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
-
D.
Reformed synod
A Reformed synod is an official governing assembly of ministers and elders within Reformed churches that meets to deliberate, decide, and provide oversight on doctrinal, disciplinary, and organizational matters.
-
E.
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.
- F. None of above. chosen
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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.