Triple
T33255629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transylvania Presbytery |
E851369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Presbyterian presbytery |
C37569
|
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 presbytery Context triple: [Transylvania Presbytery, instanceOf, Presbyterian presbytery]
-
A.
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.
-
B.
Presbyterian organization
chosen
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.
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.
-
D.
governing body of the Church of Scotland
The governing body of the Church of Scotland is the General Assembly, a representative council of ministers, elders, and other members that meets to make decisions on doctrine, policy, and administration for the national church.
-
E.
Anglican provincial synod
An Anglican provincial synod is the governing assembly of bishops, clergy, and lay representatives within an Anglican province that meets to deliberate, legislate, and make decisions on doctrine, worship, 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.