Triple
T674961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesiastical Province of New York |
E13057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Catholic ecclesiastical jurisdiction |
C575
|
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: Roman Catholic ecclesiastical jurisdiction Context triple: [Ecclesiastical Province of New York, instanceOf, Roman Catholic ecclesiastical jurisdiction]
-
A.
Roman Catholic diocese
A Roman Catholic diocese is a territorial division of the Church under the pastoral care and governance of a bishop, responsible for overseeing the spiritual, administrative, and sacramental life of the faithful within its boundaries.
-
B.
Latin Catholic diocese
A Latin Catholic diocese is a territorial ecclesiastical jurisdiction of the Latin Church, governed by a bishop who oversees the pastoral care, administration, and spiritual life of Catholics within its boundaries.
-
C.
Roman Catholic archdiocese
A Roman Catholic archdiocese is a primary ecclesiastical jurisdiction of the Catholic Church, led by an archbishop, that oversees a central territory and often has authority over neighboring dioceses within an ecclesiastical province.
-
D.
ecclesiastical jurisdiction
chosen
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.
-
E.
Roman Catholic church
A Roman Catholic church is a Christian place of worship that serves as a local community’s center for liturgy, sacraments, and prayer within the Roman Catholic tradition.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.