Triple
T34812057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form of Government (Presbyterian Church (U.S.A.)) |
E1003524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church constitutional document section |
C17410
|
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: church constitutional document section Context triple: [Form of Government (Presbyterian Church (U.S.A.)), instanceOf, church constitutional document section]
-
A.
section of religious constitution
chosen
A section of religious constitution is a distinct, formally defined subdivision within a religious organization's foundational governing document that outlines specific doctrines, rules, or organizational structures.
-
B.
church document
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
-
C.
denominational constitution
A denominational constitution is a formal governing document that defines the beliefs, organizational structure, authority, and operational rules of a religious denomination.
-
D.
section of doctrinal statement
A section of doctrinal statement is a distinct, thematically organized subdivision of a formal belief document that articulates specific theological positions or teachings within the overall doctrinal framework.
-
E.
chapter of a conciliar document
A chapter of a conciliar document is a major, thematically unified division within an official council text that organizes and develops a specific aspect of the council’s teaching or decisions.
- 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.