Triple
T7190335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocesan convention |
E167674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Episcopal Church structure |
C2300
|
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 Church structure Context triple: [Diocesan convention, instanceOf, Episcopal Church 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.
Anglican church
An Anglican church is a Christian place of worship belonging to the Anglican Communion, characterized by a liturgical tradition that blends elements of Catholic and Reformed practices.
-
C.
Anglican Communion institution
An Anglican Communion institution is an organization, body, or entity formally associated with or serving the global fellowship of autonomous Anglican churches, supporting their shared mission, governance, worship, or theological identity.
-
D.
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.
-
E.
Anglican episcopal conference
chosen
An Anglican episcopal conference is a formal assembly of Anglican bishops within a particular region or province that meets to coordinate doctrine, governance, pastoral practice, and common mission for the churches under their oversight.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.