Triple
T10992803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Missal tradition |
E259790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Catholic liturgical usage |
C11424
|
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: Anglo-Catholic liturgical usage Context triple: [Anglican Missal tradition, instanceOf, Anglo-Catholic liturgical usage]
-
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.
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.
liturgical use
chosen
Liturgical use refers to the employment of texts, objects, music, or actions within the structured public worship and ritual practices of a religious tradition.
-
D.
Western liturgical tradition
The Western liturgical tradition is the historical and theological stream of Christian worship practices, rites, and calendars that developed primarily in Western Europe, especially within the Roman Catholic, Anglican, and Protestant churches.
-
E.
Eastern Christian liturgy
Eastern Christian liturgy is the traditional, ritualized form of communal worship in Eastern Christian churches, characterized by highly structured prayers, chants, symbols, and sacraments that express and enact the church’s theology and spiritual life.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.