Triple
T31686295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Discipline of the Orthodox Presbyterian Church |
E808670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | denominational 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: denominational standard Context triple: [Book of Discipline of the Orthodox Presbyterian Church, instanceOf, denominational standard]
-
A.
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.
-
B.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
C.
ecclesiastical approval
Ecclesiastical approval is the formal authorization or endorsement granted by a religious authority, typically within a church hierarchy, indicating that a doctrine, text, action, or institution is consistent with its faith and moral teachings.
-
D.
official standard
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
-
E.
standardized designation
A standardized designation is an officially recognized and consistently applied label or title used to identify and categorize entities, roles, or items according to established norms or criteria.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:06 p.m.