Triple
T38663032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homilies of the Church of England |
E940382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican formularies |
C750
|
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 formularies Context triple: [Homilies of the Church of England, instanceOf, Anglican formularies]
-
A.
Anglican liturgical text
chosen
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 agency
An Anglican agency is an organization established by or affiliated with the Anglican Church to carry out its mission through activities such as education, social services, evangelism, and community development.
-
C.
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.
-
D.
structure for former Anglicans
A structure for former Anglicans is an organized ecclesial framework or community designed to receive, support, and integrate individuals or groups who have left the Anglican tradition while preserving elements of their spiritual and liturgical heritage.
-
E.
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.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.