Triple
T19013299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome's biblical commentaries |
E465281
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical commentary collection |
C9143
|
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: biblical commentary collection Context triple: [Jerome's biblical commentaries, instanceOf, biblical commentary collection]
-
A.
biblical commentary series
chosen
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.
-
B.
Jewish biblical commentary
Jewish biblical commentary is a tradition of interpretive writings that explain, analyze, and expand upon the Hebrew Bible’s text, language, and meaning from religious, legal, ethical, and historical perspectives.
-
C.
biblical studies resource
A biblical studies resource is a tool, text, or digital aid designed to support the scholarly and devotional study, interpretation, and teaching of the Bible and its historical, literary, and theological contexts.
-
D.
Biblical commentator
A biblical commentator is a scholar or writer who analyzes, interprets, and explains biblical texts to clarify their meaning, context, and relevance.
-
E.
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.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.