Triple
T7290917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directory for the Application of Principles and Norms on Ecumenism |
E164389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecumenical directory |
C22298
|
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: ecumenical directory Context triple: [Directory for the Application of Principles and Norms on Ecumenism, instanceOf, ecumenical directory]
-
A.
ecumenical organization
An ecumenical organization is a group or body that promotes cooperation, dialogue, and unity among different Christian denominations while respecting their distinct traditions and beliefs.
-
B.
set of ecumenical councils
A set of ecumenical councils is a collection of formally convened universal church assemblies recognized for authoritatively defining doctrine, discipline, and responses to major theological or ecclesial controversies.
-
C.
communion of churches
A communion of churches is an association of autonomous Christian churches that recognize each other’s ministries and sacraments, and share a common faith, doctrine, and ecclesial life while retaining their own governance structures.
-
D.
ecumenical dialogue commission
An ecumenical dialogue commission is a formal body composed of representatives from different Christian traditions tasked with fostering theological discussion, mutual understanding, and cooperative initiatives toward greater church unity.
-
E.
ecumenical decree
An ecumenical decree is an authoritative formal decision or doctrinal statement issued by an ecumenical council of the Church, binding on the whole Christian community it governs.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3 p.m.