Triple
T38697299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Episcopal congregations |
E950037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Episcopal congregations |
C747
|
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 congregations Context triple: [Mississippi Episcopal congregations, instanceOf, Episcopal congregations]
-
A.
Anglican dioceses
Anglican dioceses are regional ecclesiastical jurisdictions within the Anglican Communion, each overseen by a bishop who provides spiritual leadership, governance, and pastoral care to the churches and clergy in that area.
-
B.
institution of the Episcopal Church
chosen
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.
-
C.
Anglican episcopal conference
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.
-
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.
Episcopal Church resource
An Episcopal Church resource is any material, tool, or reference—such as liturgical texts, educational curricula, or pastoral guides—created to support the worship, governance, teaching, and mission of the Episcopal Church.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.