Triple
T31635947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conservative Congregational Christian Conference |
E807313
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | evangelical Protestant association |
C7156
|
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: evangelical Protestant association Context triple: [Conservative Congregational Christian Conference, instanceOf, evangelical Protestant association]
-
A.
evangelical organization
chosen
An evangelical organization is a Christian group or institution dedicated to spreading the gospel, fostering personal faith in Jesus Christ, and promoting biblical teachings through worship, outreach, and service.
-
B.
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.
-
C.
Baptist organization
A Baptist organization is a structured group or institution that advances Baptist Christian beliefs and practices through worship, education, missions, and community service.
-
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.
evangelical network
An evangelical network is a loosely organized yet interconnected group of individuals, churches, and organizations that share and promote evangelical Christian beliefs, resources, and activities across various social, cultural, and media channels.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:47 p.m.