Triple
T28337971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Maserfelth |
E717729
|
entity |
| Predicate | belligerentLeaderKilled |
P101086
|
FINISHED |
| Object | Oswald of Northumbria |
—
|
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: Oswald of Northumbria | Statement: [Battle of Maserfelth, belligerentLeaderKilled, Oswald of Northumbria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentLeaderKilled Context triple: [Battle of Maserfelth, belligerentLeaderKilled, Oswald of Northumbria]
-
A.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
B.
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.
-
C.
deathOfLeader
Indicates that a leader has died, marking the end of their leadership due to death.
-
D.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
-
E.
alliedCommanderKilled
Indicates that a commander belonging to an allied force has been killed.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bd68ac08190b35887261657a408 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:37 a.m.