Triple
T33234613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of Jesus |
E850790
|
entity |
| Predicate | treatsMiraclesAs |
P179080
|
FINISHED |
| Object | legendary or symbolic accounts |
—
|
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: legendary or symbolic accounts | Statement: [Life of Jesus, treatsMiraclesAs, legendary or symbolic accounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsMiraclesAs Context triple: [Life of Jesus, treatsMiraclesAs, legendary or symbolic accounts]
-
A.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
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.
-
C.
associatedWithMiracle
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
D.
requiresMiracleFor
Indicates that one entity can only achieve, obtain, or accomplish the other entity if an extraordinary or miraculous event occurs.
-
E.
recognizedAsMiraculous
Indicates that something is acknowledged or officially deemed to be miraculous, often by an authority or community.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:31 a.m.