Triple
T4768223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisha |
E105862
|
entity |
| Predicate | posthumousMiracle |
P59232
|
FINISHED |
| Object | reviving a dead man who touched his bones |
—
|
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: reviving a dead man who touched his bones | Statement: [Elisha, posthumousMiracle, reviving a dead man who touched his bones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousMiracle Context triple: [Elisha, posthumousMiracle, reviving a dead man who touched his bones]
-
A.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
posthumousReputation
Indicates the reputation or standing attributed to a person after their death.
-
C.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
D.
posthumousLegalStatus
Indicates the legal condition or recognition assigned to a person or entity after their death.
-
E.
miracleDescription
Indicates that a miraculous event or phenomenon is being described or characterized.
- F. None of above. chosen
Provenance (4 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:21 p.m.