Triple
T25364645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessed |
E636065
|
entity |
| Predicate | requiresMiracleFor |
P166118
|
FINISHED |
| Object | non-martyr candidates |
—
|
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: non-martyr candidates | Statement: [Blessed, requiresMiracleFor, non-martyr candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMiracleFor Context triple: [Blessed, requiresMiracleFor, non-martyr candidates]
-
A.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
B.
associatedWithMiracle
Indicates a relationship in which something is connected to, involved in, or characterized by a miracle.
-
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.
hasMiracleScene
Indicates that a scene involves a miraculous or supernatural event occurring.
-
E.
miracleQuestionedBy
Indicates that the occurrence or authenticity of a miracle is being doubted, challenged, or critically examined by someone.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 21, 2026, 1:36 p.m.