Triple
T4604073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homilies on Genesis |
E100386
|
entity |
| Predicate | typeOfExegesis |
P18616
|
FINISHED |
| Object | spiritual exegesis |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: spiritual exegesis | Statement: [Homilies on Genesis, typeOfExegesis, spiritual exegesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExegesis Context triple: [Homilies on Genesis, typeOfExegesis, spiritual exegesis]
-
A.
styleOfExegesis
chosen
Indicates the particular interpretive method or approach applied when analyzing or explaining a text.
-
B.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
D.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
E.
theologicalInterpretation
Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69bd5999f9c88190a43309573df61159 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.