Triple
T4152117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homilies on the Gospel of John |
E89930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patristic commentary |
C12852
|
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: patristic commentary Context triple: [Homilies on the Gospel of John, instanceOf, patristic commentary]
-
A.
patristic text
chosen
A patristic text is a written work authored by an early Christian theologian or Church Father, typically from the first to eighth centuries, that contributes to the development of Christian doctrine, exegesis, and pastoral teaching.
-
B.
biblical commentary series
A biblical commentary series is a structured collection of scholarly works that systematically explain, interpret, and contextualize the books of the Bible, often volume by volume or section by section.
-
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.
method of biblical exegesis
A method of biblical exegesis is a systematic approach or set of interpretive principles used to analyze, explain, and derive meaning from biblical texts within their historical, literary, and theological 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:44 p.m.