Triple
T2897465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Church as Communion |
E63975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican–Roman Catholic dialogue text |
C11657
|
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: Anglican–Roman Catholic dialogue text Context triple: [The Church as Communion, instanceOf, Anglican–Roman Catholic dialogue text]
-
A.
Anglican liturgical text
An Anglican liturgical text is a formal written resource used in Anglican worship that provides structured prayers, readings, and rites for services throughout the liturgical year.
-
B.
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.
-
C.
Anglican church
An Anglican church is a Christian place of worship belonging to the Anglican Communion, characterized by a liturgical tradition that blends elements of Catholic and Reformed practices.
-
D.
Anglican episcopal conference
An Anglican episcopal conference is a formal assembly of Anglican bishops within a particular region or province that meets to coordinate doctrine, governance, pastoral practice, and common mission for the churches under their oversight.
-
E.
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.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:08 p.m.