Triple
T25813963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Institution of a Christian Man |
E650198
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican foundational document |
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 foundational document Context triple: [The Institution of a Christian Man, instanceOf, Anglican foundational document]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
organ of the Church of England
An organ of the Church of England is a formal body or instrument—such as a synod, bishop, or ecclesiastical court—through which the Church carries out its governance, decision-making, and official functions.
-
E.
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.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:12 a.m.