Triple
T12308730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | joint Catholic–Orthodox declaration of 1965 |
E293422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic–Orthodox ecumenical agreement |
C27467
|
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: Catholic–Orthodox ecumenical agreement Context triple: [joint Catholic–Orthodox declaration of 1965, instanceOf, Catholic–Orthodox ecumenical agreement]
-
A.
Catholic–Orthodox body
A Catholic–Orthodox body is an organized group, institution, or commission that brings together members of the Roman Catholic and Eastern Orthodox Churches for dialogue, cooperation, and the pursuit of closer ecclesial unity.
-
B.
ecumenical agreement
chosen
An ecumenical agreement is a formal understanding or accord between different Christian denominations aimed at fostering unity, cooperation, and mutual recognition in faith and practice.
-
C.
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.
-
D.
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.
-
E.
Anglican–Roman Catholic dialogue text
An Anglican–Roman Catholic dialogue text is an official or semi-official document recording theological discussions, agreements, and points of divergence between Anglican and Roman Catholic representatives in ecumenical dialogue.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.