Triple
T531113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Hildesheim |
E12223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin Catholic diocese |
C4229
|
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: Latin Catholic diocese Context triple: [Roman Catholic Diocese of Hildesheim, instanceOf, Latin Catholic diocese]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
Roman Catholic mission network
A Roman Catholic mission network is an organized system of churches, religious orders, and agencies that coordinate evangelization, pastoral care, education, and charitable works to spread and sustain the Catholic faith across different regions and cultures.
- F. None of above. chosen
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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.