Triple
T22320271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesleyan Quadrilateral |
E551764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Methodist theology 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 theology concept Context triple: [Wesleyan Quadrilateral, instanceOf, Methodist theology 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.
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.
-
C.
Methodist organization
A Methodist organization is a structured group or institution that operates according to Methodist Christian beliefs, practices, and governance to support worship, ministry, and community service.
-
D.
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.
-
E.
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.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.