Triple
T14855271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of the Holy Eucharist |
E349334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican theological work |
C5743
|
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 theological work Context triple: [The Doctrine of the Holy Eucharist, instanceOf, Anglican theological work]
-
A.
theological work
chosen
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
B.
Anglican tradition
The Anglican tradition is a Christian faith stream rooted in the Church of England that blends Catholic and Reformed elements, emphasizing liturgical worship, the authority of Scripture, and a via media (middle way) in theology and practice.
-
C.
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.
-
D.
Anglican article
An Anglican article is a formal doctrinal statement within Anglicanism, most notably one of the Thirty-Nine Articles, that defines key theological beliefs and practices of the Anglican Church.
-
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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:54 a.m.