Triple
T5175992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deianira |
E116798
|
entity |
| Predicate | motiveForSendingTunic |
P19457
|
FINISHED |
| Object | fear of losing Heracles' affection |
—
|
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: fear of losing Heracles' affection | Statement: [Deianira, motiveForSendingTunic, fear of losing Heracles' affection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motiveForSendingTunic Context triple: [Deianira, motiveForSendingTunic, fear of losing Heracles' affection]
-
A.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
-
B.
sentMissionTo
Indicates that one entity dispatched or assigned another entity to carry out a specific mission at a particular destination or context.
-
C.
sentOnMissionBy
Indicates that one entity was assigned or dispatched on a mission by another entity.
-
D.
motivationFor
chosen
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.