Triple
T9129100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crossing of the Jordan River |
E219037
|
entity |
| Predicate | hasMiraculousSign |
P61934
|
FINISHED |
| Object | waters of the Jordan stopped |
—
|
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: waters of the Jordan stopped | Statement: [crossing of the Jordan River, hasMiraculousSign, waters of the Jordan stopped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiraculousSign Context triple: [crossing of the Jordan River, hasMiraculousSign, waters of the Jordan stopped]
-
A.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
B.
associatedWithMiracle
chosen
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
C.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
D.
hasMiraculousBirth
Indicates that an entity comes into existence through a supernatural, extraordinary, or otherwise non-natural birth event.
-
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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cc85b081908ee80db0e3b7df15 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.