Triple
T28782597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Alabama Conference of the United Methodist Church |
E726714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Methodist Church jurisdictional unit |
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: United Methodist Church jurisdictional unit Context triple: [North Alabama Conference of the United Methodist Church, instanceOf, United Methodist Church jurisdictional unit]
-
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.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a shared governance, worship life, and mission.
-
C.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a common organizational and theological framework.
-
D.
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.
-
E.
Baptist church
A Baptist church is a Christian congregation that emphasizes believer’s baptism by full immersion, congregational governance, and the authority of the Bible in faith 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:20 a.m.