Triple
T22778849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cape Bon |
E563777
|
entity |
| Predicate | AlliedLosses |
P17247
|
FINISHED |
| Object | no ships lost |
—
|
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: no ships lost | Statement: [Battle of Cape Bon, AlliedLosses, no ships lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlliedLosses Context triple: [Battle of Cape Bon, AlliedLosses, no ships lost]
-
A.
casualtiesAllied
chosen
Indicates the number or extent of losses (killed, wounded, or missing) suffered by allied forces in a conflict or incident.
-
B.
aircraftLosses
Indicates the number or occurrence of aircraft that have been destroyed, damaged beyond repair, or otherwise lost.
-
C.
AlliedShipsInvolved
Indicates that allied ships participated in or were involved in the specified event or operation.
-
D.
troopStrengthAlliedApprox
Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
-
E.
aircraftLostByAllies
Indicates that the specified aircraft was lost by Allied forces (e.g., destroyed, missing, or otherwise no longer operational under their control).
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b631c6881908a6687920923dcf4 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.