Triple
T21475654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancastrian forces |
E529853
|
entity |
| Predicate | outcomeAtBattleOfTowton |
P19109
|
FINISHED |
| Object | decisive defeat |
—
|
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: decisive defeat | Statement: [Lancastrian forces, outcomeAtBattleOfTowton, decisive defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeAtBattleOfTowton Context triple: [Lancastrian forces, outcomeAtBattleOfTowton, decisive defeat]
-
A.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
B.
outcomeForCharlesI
Indicates the resulting fate, consequence, or end state that befell Charles I as a result of preceding events or actions.
-
C.
roleInWarsOfTheRoses
Indicates the specific part or function an entity played in the historical conflict known as the Wars of the Roses.
-
D.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1737f881908ef7889e9568a4d3 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:19 p.m.