Triple
T18295527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belokrinitskaya hierarchy |
E438220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episcopal structure |
C2176
|
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: episcopal structure Context triple: [Belokrinitskaya hierarchy, instanceOf, episcopal structure]
-
A.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
-
B.
Episcopal chapel
An Episcopal chapel is a small, often intimate place of Christian worship affiliated with the Episcopal Church, used for prayer, liturgy, and sacramental services.
-
C.
ecclesiastical institution
chosen
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
D.
particular church structure
A particular church structure is an individual, organized Christian community or congregation, with its own governance and physical or communal framework, that forms a distinct unit within the broader Church.
-
E.
structure for former Anglicans
A structure for former Anglicans is an organized ecclesial framework or community designed to receive, support, and integrate individuals or groups who have left the Anglican tradition while preserving elements of their spiritual and liturgical heritage.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.