Triple
T965933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Worcester (1651) |
E20836
|
entity |
| Predicate | casualtiesRoyalist |
P1399
|
FINISHED |
| Object | several thousand killed |
—
|
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: several thousand killed | Statement: [Battle of Worcester (1651), casualtiesRoyalist, several thousand killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesRoyalist Context triple: [Battle of Worcester (1651), casualtiesRoyalist, several thousand killed]
-
A.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
B.
RoyalistForceStrength
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
C.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
casualtiesUKKilled
Indicates that the relationship specifies the number of people from the UK who were killed in the referenced event or incident.
-
E.
royalistObjective
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b431d61481908b53490e99670363 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.