Triple
T28337988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Maserfelth |
E717729
|
entity |
| Predicate | notableFigureKilled |
P123847
|
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, notableFigureKilled, Oswald of Northumbria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFigureKilled Context triple: [Battle of Maserfelth, notableFigureKilled, Oswald of Northumbria]
-
A.
notablePersonKilledThere
chosen
Indicates that a notable or famous person was killed at the referenced location.
-
B.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
C.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
-
D.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
E.
notablePrisonerExecuted
Indicates that a person, recognized as a notable or significant prisoner, was executed while in custody.
- 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_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 28, 2026, 12:37 a.m.