Triple
T29772410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesleyan Covenant |
E755284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Methodist theological concept |
C38948
|
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: Methodist theological concept Context triple: [Wesleyan Covenant, instanceOf, Methodist theological concept]
-
A.
Methodist doctrinal source
chosen
A Methodist doctrinal source is an authoritative text, tradition, or teaching (such as Scripture, the Wesleyan Quadrilateral, or official church statements) that shapes and defines Methodist beliefs and practices.
-
B.
Protestant theological movement
A Protestant theological movement is a distinct stream within Protestant Christianity characterized by shared doctrinal emphases, interpretive approaches to Scripture, and practical expressions of faith that differentiate it from other Protestant traditions.
-
C.
theological concept
A theological concept is an abstract idea or principle used to understand, explain, or systematize beliefs about the nature of the divine, spiritual realities, and their relationship to the world and humanity.
-
D.
Trinitarian theological view
A Trinitarian theological view is a Christian doctrinal perspective that understands God as one divine being eternally existing in three distinct, co-equal, and co-eternal persons: Father, Son, and Holy Spirit.
-
E.
Methodist
A Methodist is a member of a Protestant Christian tradition that emphasizes personal faith, disciplined spiritual practice, social justice, and the theology and organizational patterns rooted in the teachings of John Wesley.
- 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.