Triple
T36006425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gennaro di Napoli |
E1041282
|
entity |
| Predicate | hasMiracleType |
P59063
|
FINISHED |
| Object | blood liquefaction |
—
|
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: blood liquefaction | Statement: [Gennaro di Napoli, hasMiracleType, blood liquefaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiracleType Context triple: [Gennaro di Napoli, hasMiracleType, blood liquefaction]
-
A.
miracleType
chosen
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
hasMiracleScene
Indicates that a scene involves a miraculous or supernatural event occurring.
-
C.
requiresMiracleFor
Indicates that one entity can only achieve, obtain, or accomplish the other entity if an extraordinary or miraculous event occurs.
-
D.
hasMysteryType
Indicates that an entity is associated with, categorized under, or characterized by a particular type whose nature or classification is unknown, hidden, or unspecified.
-
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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:07 p.m.