Triple
T4604032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homilies on Genesis |
E100386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian homiletic text |
C6260
|
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 homiletic text Context triple: [Homilies on Genesis, instanceOf, Christian homiletic text]
-
A.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
-
B.
Christian ecumenical text
A Christian ecumenical text is a written work intended to foster unity, dialogue, and shared understanding among different Christian denominations by emphasizing common beliefs and cooperative practices.
-
C.
Christian sermon
chosen
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.
-
D.
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.
-
E.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.