Triple
T17969304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Corunna |
E449291
|
entity |
| Predicate | BritishForceRole |
P129947
|
FINISHED |
| Object | rearguard for embarkation |
—
|
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: rearguard for embarkation | Statement: [Battle of Corunna, BritishForceRole, rearguard for embarkation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishForceRole Context triple: [Battle of Corunna, BritishForceRole, rearguard for embarkation]
-
A.
BritishForcesType
Indicates that an entity is classified as a type or category within the British armed forces.
-
B.
militaryForceInvolved (British)
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
C.
strengthBritishForces
Indicates the numerical size or combat capacity of British military forces in a given context or operation.
-
D.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
E.
isVolunteerForce
Indicates that a group or force is composed of individuals who serve voluntarily rather than by conscription or obligation.
- F. None of above. chosen
Provenance (4 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13b1b088190b7d71006b31e5cc3 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.