Triple
T9705791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Joseph of Cupertino |
E234893
|
entity |
| Predicate | notableMiracleTradition |
P73224
|
FINISHED |
| Object | levitation during Mass |
—
|
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: levitation during Mass | Statement: [Saint Joseph of Cupertino, notableMiracleTradition, levitation during Mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMiracleTradition Context triple: [Saint Joseph of Cupertino, notableMiracleTradition, levitation during Mass]
-
A.
miracleTradition
chosen
Indicates that a miracle is associated with, preserved in, or transmitted through a particular religious or cultural tradition.
-
B.
numberOfMiraclesTraditionallyAssociated
Indicates the traditionally recognized count of miracles that are associated with a particular entity or subject.
-
C.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
D.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
E.
associatedWithMiracle
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da369b4819081f6ce01289ed725 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.