Triple
T23934983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kishon |
E602607
|
entity |
| Predicate | aftermathEvent |
P48782
|
FINISHED |
| Object | killing of Sisera by Jael |
—
|
NE NERFINISHED |
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: killing of Sisera by Jael | Statement: [Battle of Kishon, aftermathEvent, killing of Sisera by Jael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermathEvent Context triple: [Battle of Kishon, aftermathEvent, killing of Sisera by Jael]
-
A.
aftermathOf
chosen
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
B.
aftermathActivity
Indicates the activity or state that occurs as a direct consequence of, or in response to, a preceding event or situation.
-
C.
aftermathDescription
Indicates the description or characterization of events, conditions, or consequences that occur following a particular incident or action.
-
D.
aftermathDepictedIn
Indicates that the aftermath or consequences of an event or situation are depicted or represented in a given medium or work.
-
E.
aftermathPolicy
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9e8abc8190a3028a358265912e |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9 p.m.