Triple
T2563829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article XVII Of Predestination and Election |
E57303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican doctrinal text |
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 doctrinal text Context triple: [Article XVII Of Predestination and Election, instanceOf, Anglican doctrinal text]
-
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 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.
-
C.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
-
D.
Anglican Communion institution
An Anglican Communion institution is an organization, body, or entity formally associated with or serving the global fellowship of autonomous Anglican churches, supporting their shared mission, governance, worship, or theological identity.
-
E.
Anglican clerical position
An Anglican clerical position is an official role within the Anglican Church’s ordained or licensed ministry structure, encompassing responsibilities for worship, pastoral care, administration, and spiritual leadership in a parish or wider ecclesiastical jurisdiction.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.