Triple
T151241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Canterbury |
E3436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical province |
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: ecclesiastical province Context triple: [Province of Canterbury, instanceOf, ecclesiastical province]
-
A.
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.
-
B.
Catholic Church council
A Catholic Church council is a formal assembly of bishops and other church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
C.
Catholic bishop
A Catholic bishop is a high-ranking ordained minister in the Catholic Church who possesses the fullness of the sacrament of Holy Orders and is responsible for teaching doctrine, governing a diocese, and sanctifying the faithful through the sacraments.
-
D.
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.
-
E.
Catholic Church
The Catholic Church is a worldwide Christian religious institution, led by the Pope, that traces its origins to Jesus Christ and the apostles and is characterized by a hierarchical structure, sacramental worship, and a unified body of doctrine.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.