Triple
T23152059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Bishops Conference |
E578346
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional bishops conference |
C19200
|
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: regional bishops conference Context triple: [Nordic Bishops Conference, instanceOf, regional bishops conference]
-
A.
Catholic bishops’ conference
chosen
A Catholic bishops’ conference is an official assembly of bishops from a particular country or region who collaborate to discuss, coordinate, and implement pastoral, liturgical, and doctrinal policies for the local Church in communion with the Holy See.
-
B.
organ of a bishops’ conference
An organ of a bishops’ conference is a structured body or committee established by the conference to carry out specific functions such as governance, coordination, pastoral planning, or administration on behalf of the member bishops.
-
C.
group of dioceses
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
-
D.
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.
-
E.
ecumenical conference
An ecumenical conference is a formal gathering of representatives from different Christian denominations, and sometimes other faiths, convened to discuss theological issues, promote unity, and coordinate cooperative action.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.