Triple
T207148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savior |
E4633
|
entity |
| Predicate | emphasizesAspectOfJesus |
P2318
|
FINISHED |
| Object | forgiveness of sins |
—
|
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: forgiveness of sins | Statement: [Savior, emphasizesAspectOfJesus, forgiveness of sins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesAspectOfJesus Context triple: [Savior, emphasizesAspectOfJesus, forgiveness of sins]
-
A.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
B.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
C.
hasEcclesiologicalDimension
Indicates that something possesses a significance, aspect, or implication related to the nature, structure, or life of the Church as a community.
-
D.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
E.
roleInSalvationHistory
chosen
Indicates the specific function or significance an entity has within the overarching narrative or process of salvation history.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.