Triple
T29772412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesleyan Covenant |
E755284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wesleyan tradition concept |
C54573
|
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: Wesleyan tradition concept Context triple: [Wesleyan Covenant, instanceOf, Wesleyan tradition concept]
-
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.
university tradition
A university tradition is a recurring, institution-specific practice or ritual that embodies the shared history, values, and identity of a university community.
-
C.
Christian ecclesial tradition
chosen
The Christian ecclesial tradition is the historically continuous, community-shaped pattern of faith, worship, doctrine, and governance that structures how Christians live, interpret, and hand on their understanding of the gospel across time.
-
D.
Puritan practice
Puritan practice is the disciplined, community-oriented application of strict moral, religious, and social codes derived from a literal interpretation of Scripture, shaping daily life, worship, and governance.
-
E.
Jesuit educational tradition
The Jesuit educational tradition is a holistic, values-driven approach to learning that emphasizes intellectual rigor, critical thinking, ethical formation, and service to others in the pursuit of faith, justice, and the common good.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:43 p.m.