Triple
T11390713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canons of the Episcopal Diocese of New York |
E269827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diocesan canons |
C2706
|
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: diocesan canons Context triple: [Canons of the Episcopal Diocese of New York, instanceOf, diocesan canons]
-
A.
ecclesiastical law code
chosen
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
-
B.
diocesan convention
A diocesan convention is a formal governing assembly of clergy and lay representatives within a diocese that meets to conduct official church business, set policies, and oversee the mission and administration of the diocese.
-
C.
ecclesiastical jurisdiction
An ecclesiastical jurisdiction is a defined territorial or personal area of authority within a religious organization, governed by church law and overseen by designated clerical leaders.
-
D.
Byzantine supplicatory canon
A Byzantine supplicatory canon is a structured liturgical hymn composed of multiple odes, chanted in the Eastern Christian tradition to implore divine mercy, aid, or intercession, often addressed to Christ, the Theotokos, or specific saints.
-
E.
synodal lineamenta
Synodal lineamenta are preliminary guiding documents issued by Church authorities to outline themes, questions, and directions for reflection and discussion in preparation for a synod.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.