Triple
T18917691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 6 |
E462762
|
entity |
| Predicate | containsMiracle |
P104496
|
FINISHED |
| Object | Jesus walking on the Sea of Galilee |
—
|
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 walking on the Sea of Galilee | Statement: [John 6, containsMiracle, Jesus walking on the Sea of Galilee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMiracle Context triple: [John 6, containsMiracle, Jesus walking on the Sea of Galilee]
-
A.
hasMiracleScene
chosen
Indicates that a scene involves a miraculous or supernatural event occurring.
-
B.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
C.
associatedWithMiracle
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
D.
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.
-
E.
miracleDescription
Indicates that a miraculous event or phenomenon is being described or characterized.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c62884988190a362ada1a0a47134 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.