Triple
T34812009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundations of Presbyterian Polity |
E1003523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Presbyterian Church (U.S.A.) constitutional standard |
C34156
|
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 Church (U.S.A.) constitutional standard Context triple: [Foundations of Presbyterian Polity, instanceOf, Presbyterian Church (U.S.A.) constitutional standard]
-
A.
Presbyterian polity document
A Presbyterian polity document is a formal text that outlines the governance structure, rules, procedures, and doctrinal standards by which a Presbyterian church or denomination is organized and administered.
-
B.
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.
-
C.
denominational constitution
chosen
A denominational constitution is a formal governing document that defines the beliefs, organizational structure, authority, and operational rules of a religious denomination.
-
D.
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.
-
E.
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.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.