Triple
T22722901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | exorcism of Asmodeus |
E561911
|
entity |
| Predicate | outcomeForSarah |
P149458
|
FINISHED |
| Object | ability to consummate marriage safely |
—
|
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: ability to consummate marriage safely | Statement: [exorcism of Asmodeus, outcomeForSarah, ability to consummate marriage safely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForSarah Context triple: [exorcism of Asmodeus, outcomeForSarah, ability to consummate marriage safely]
-
A.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
C.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
D.
outcomeForMatilda
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Matilda.
-
E.
outcomeForZenobia
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Zenobia.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17927e0348190a4dba430563ef155 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:20 p.m.