Triple
T10992802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Missal tradition |
E259790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican liturgical tradition |
C9527
|
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 liturgical tradition Context triple: [Anglican Missal tradition, instanceOf, Anglican liturgical tradition]
-
A.
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.
-
B.
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.
-
C.
Western liturgical tradition
chosen
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.
-
D.
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.
-
E.
Evangelical Anglican
An Evangelical Anglican is a member of the Anglican tradition who emphasizes the authority of Scripture, personal conversion, and active evangelism within the framework of Anglican liturgy and theology.
- 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.