Triple
T17082899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenus |
E414517
|
entity |
| Predicate | reactionToDefeat |
P90365
|
FINISHED |
| Object | killed the remaining suitors |
—
|
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: killed the remaining suitors | Statement: [Evenus, reactionToDefeat, killed the remaining suitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionToDefeat Context triple: [Evenus, reactionToDefeat, killed the remaining suitors]
-
A.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
B.
afterDefeat
Indicates that one event, state, or action occurs subsequent to and as a consequence of a defeat of some party or entity.
-
C.
defeatEffect
Indicates that one entity’s defeat causes a particular outcome or change to occur for another entity or the overall situation.
-
D.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
E.
treatmentAfterDefeat
chosen
Indicates that one entity’s treatment of another occurs subsequent to that other entity’s defeat.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe4d3908190b23ce3c2d3fe7d14 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.