Triple
T27260365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on the Psalms |
E687744
|
entity |
| Predicate | hermeneutic |
P21759
|
FINISHED |
| Object | grammatical-historical interpretation |
—
|
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: grammatical-historical interpretation | Statement: [Commentary on the Psalms, hermeneutic, grammatical-historical interpretation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hermeneutic Context triple: [Commentary on the Psalms, hermeneutic, grammatical-historical interpretation]
-
A.
styleOfExegesis
Indicates the particular interpretive method or approach applied when analyzing or explaining a text.
-
B.
theologicalInterpretation
Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
-
C.
מאפיין פרשנות
Indicates that something characterizes or defines a particular interpretation.
-
D.
HnInterpretation
Indicates that one entity serves as an interpretation, explanation, or semantic mapping of another entity (such as a text, symbol, or data).
-
E.
interpretationMethod
chosen
Indicates the method, technique, or process used to interpret or derive meaning from something.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626ee531c81908f23232136023c66 |
completed | May 2, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:52 a.m.