Triple
T27903098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Winwaed |
E705688
|
entity |
| Predicate | combatantLeaderKilled |
P101086
|
FINISHED |
| Object | Penda of Mercia |
—
|
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: Penda of Mercia | Statement: [Battle of the Winwaed, combatantLeaderKilled, Penda of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantLeaderKilled Context triple: [Battle of the Winwaed, combatantLeaderKilled, Penda of Mercia]
-
A.
combatantLeaderKilledOrMortallyWounded
chosen
Indicates that the leader of a combatant force was killed outright or suffered wounds that were fatal in the context of the conflict or engagement.
-
B.
alliedCommanderKilled
Indicates that a commander belonging to an allied force has been killed.
-
C.
commanderOfDefeatedSide
Indicates that the subject is the military or strategic leader of the side that lost in a particular conflict or battle.
-
D.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
-
E.
commanderKilledSoonAfter
Indicates that a commander was killed shortly after a referenced event or time point.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:43 p.m.