Triple
T2077210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Days' Battle |
E44951
|
entity |
| Predicate | DutchShipsLost |
P821
|
FINISHED |
| Object | several 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: several ships lost | Statement: [Four Days' Battle, DutchShipsLost, several ships lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchShipsLost Context triple: [Four Days' Battle, DutchShipsLost, several ships lost]
-
A.
shipsSunkOrTotalLoss
chosen
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
B.
laterOutcomeOfVoyage
Indicates that one event, state, or outcome occurs as a subsequent result or later phase of a specified voyage.
-
C.
sunkCountry
Indicates that one entity (typically a vessel or force) caused the sinking of a country’s ship(s) or naval assets belonging to another country.
-
D.
livestockLostNetherlands
Indicates livestock that have died or gone missing within the Netherlands, typically as a net loss count over a given period.
-
E.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba2fa9c48190958826d5226544df |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.