Triple
T19014354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazarus’ Tomb |
E465306
|
entity |
| Predicate | miracleCommemorated |
P61934
|
FINISHED |
| Object | Jesus raising Lazarus from the dead |
—
|
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: Jesus raising Lazarus from the dead | Statement: [Lazarus’ Tomb, miracleCommemorated, Jesus raising Lazarus from the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miracleCommemorated Context triple: [Lazarus’ Tomb, miracleCommemorated, Jesus raising Lazarus from the dead]
-
A.
miracleOccurs
Indicates that an event takes place which is perceived as extraordinary, inexplicable by natural or scientific laws, and often attributed to a supernatural or divine cause.
-
B.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
C.
miracleDescription
Indicates that a miraculous event or phenomenon is being described or characterized.
-
D.
associatedWithMiracle
chosen
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
E.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6aac4dc8190ac51f22c13f1b96c |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.