Triple
T25398494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redeemer Presbyterian Church |
E636356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-denominational church network |
C7115
|
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: non-denominational church network Context triple: [Redeemer Presbyterian Church, instanceOf, non-denominational church network]
-
A.
non-denominational church
A non-denominational church is a Christian congregation that operates independently of established denominations, emphasizing core biblical teachings and contemporary worship without formal ties to a specific religious tradition.
-
B.
interdenominational Christian church
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.
-
C.
religious network
chosen
A religious network is a structured system of individuals, groups, and institutions connected by shared beliefs, practices, and organizational ties that facilitate the spread and maintenance of a religious tradition.
-
D.
federated church
A federated church is a single local congregation formed by the union of two or more distinct denominational bodies that worship and minister together while maintaining ties to their respective parent denominations.
-
E.
nontrinitarian church
A nontrinitarian church is a Christian congregation or denomination that rejects the doctrine of the Trinity, instead holding alternative views about the nature and relationship of God, Jesus Christ, and the 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:50 p.m.