Triple
T26338226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edifying Discourses in Diverse Spirits |
E662574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian discourse collection |
C17285
|
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: Christian discourse collection Context triple: [Edifying Discourses in Diverse Spirits, instanceOf, Christian discourse collection]
-
A.
Christian homiletic collection
chosen
A Christian homiletic collection is an organized compilation of sermons, homilies, or preaching materials intended for instruction, liturgical use, or spiritual edification within Christian communities.
-
B.
religious discourse collection
A religious discourse collection is an organized set of spoken, written, or multimedia texts that document, analyze, or present religious beliefs, practices, and debates across contexts and traditions.
-
C.
Biblical discourse
Biblical discourse is the structured communication—spoken, written, or interpretive—that engages with, explains, or applies the texts, themes, and theology of the Bible within specific historical, cultural, and religious contexts.
-
D.
Christian theological corpus
The Christian theological corpus is the body of writings, doctrines, and interpretive traditions that systematically articulate and reflect on Christian beliefs about God, Christ, salvation, the Church, and the ultimate destiny of creation.
-
E.
Christian sermon
A Christian sermon is a structured religious discourse delivered by a preacher to interpret Scripture, convey theological teachings, and exhort listeners to apply Christian faith in their daily lives.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:37 p.m.