Triple
T5601459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside Church |
E147129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdenominational church |
C4007
|
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: interdenominational church Context triple: [Riverside Church, instanceOf, interdenominational church]
-
A.
interdenominational Christian church
chosen
An interdenominational Christian church is a Christian congregation that welcomes and unites believers from multiple denominational backgrounds, emphasizing shared core beliefs over specific denominational doctrines.
-
B.
Unitarian Universalist church
A Unitarian Universalist church is a liberal religious community that gathers people of diverse beliefs to seek spiritual growth, practice ethical living, and promote social justice without adherence to a fixed creed.
-
C.
communion of churches
A communion of churches is an association of autonomous Christian churches that recognize each other’s ministries and sacraments, and share a common faith, doctrine, and ecclesial life while retaining their own governance structures.
-
D.
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.
-
E.
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.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:39 p.m.