Triple
T32590404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giuseppe Maria Desa |
E833046
|
entity |
| Predicate | notableMiracleType |
P59063
|
FINISHED |
| Object | levitation during prayer |
—
|
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 prayer | Statement: [Giuseppe Maria Desa, notableMiracleType, levitation during prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMiracleType Context triple: [Giuseppe Maria Desa, notableMiracleType, levitation during prayer]
-
A.
miracleType
chosen
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
recognizedAsMiraculous
Indicates that something is acknowledged or officially deemed to be miraculous, often by an authority or community.
-
C.
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.
-
D.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:05 a.m.