Triple
T5827388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bothwell Bridge |
E129260
|
entity |
| Predicate | casualtiesCovenanters |
P1399
|
FINISHED |
| Object | hundreds killed or wounded |
—
|
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: hundreds killed or wounded | Statement: [Battle of Bothwell Bridge, casualtiesCovenanters, hundreds killed or wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesCovenanters Context triple: [Battle of Bothwell Bridge, casualtiesCovenanters, hundreds killed or wounded]
-
A.
CovenanterForcesIncluded
Indicates that the forces involved included or comprised Covenanter troops or military units.
-
B.
ScottishCasualties
Indicates that an event or situation resulted in casualties (deaths or injuries) among Scottish individuals or forces.
-
C.
RoyalistCasualties
Indicates the number or occurrence of casualties suffered by Royalist forces in a given conflict or event.
-
D.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
CovenanterPoliticalAlignment
Indicates the political stance or affiliation associated with a Covenanter in relation to contemporary political factions, policies, or conflicts.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.