Triple
T15695048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Annual Conference of the Methodist Episcopal Church, South |
E380438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Methodist church body |
C13647
|
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 church body Context triple: [Mississippi Annual Conference of the Methodist Episcopal Church, South, instanceOf, Methodist church body]
-
A.
Methodist organization
chosen
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.
-
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.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
-
D.
Christian ecumenical body
A Christian ecumenical body is an organized association of churches or Christian communities from different traditions that collaborates to promote unity, shared witness, and common action in faith and practice.
-
E.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:44 a.m.