Triple
T13728707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 4 |
E329732
|
entity |
| Predicate | includesMiracle |
P104496
|
FINISHED |
| Object | healing of the royal official’s son at a distance |
—
|
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: healing of the royal official’s son at a distance | Statement: [John 4, includesMiracle, healing of the royal official’s son at a distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMiracle Context triple: [John 4, includesMiracle, healing of the royal official’s son at a distance]
-
A.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
associatedWithMiracle
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
C.
hasMiracleScene
chosen
Indicates that a scene involves a miraculous or supernatural event occurring.
-
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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.