Triple
T36306004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Holy Redeemer |
E893944
|
entity |
| Predicate | focusesOnAspectOfChrist |
P11154
|
FINISHED |
| Object | sacrificial death |
—
|
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: sacrificial death | Statement: [Most Holy Redeemer, focusesOnAspectOfChrist, sacrificial death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnAspectOfChrist Context triple: [Most Holy Redeemer, focusesOnAspectOfChrist, sacrificial death]
-
A.
emphasizesAttributeOfChrist
chosen
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Christ.
-
B.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
-
C.
viewOnChrist
Indicates a person's stance, belief, or perspective regarding Jesus Christ.
-
D.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
E.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:09 p.m.