Triple
T19110374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on St Malo (1758) |
E467771
|
entity |
| Predicate | combatantRoleOfBritain |
P42949
|
FINISHED |
| Object | attacking force |
—
|
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: attacking force | Statement: [Raid on St Malo (1758), combatantRoleOfBritain, attacking force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantRoleOfBritain Context triple: [Raid on St Malo (1758), combatantRoleOfBritain, attacking force]
-
A.
combatantRoleOfUnitedKingdom
chosen
Indicates that the specified combatant role is one that was held by, or associated with, the United Kingdom in a particular conflict or military context.
-
B.
militaryForceInvolved (British)
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
C.
BritishForceRole
Indicates that an entity serves in a specific role or capacity within a British military or armed forces context.
-
D.
strengthBritishForces
Indicates the numerical size or combat capacity of British military forces in a given context or operation.
-
E.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e393bafc81908e35a0eba7b807a6 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.