Triple
T1431115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lowestoft |
E30447
|
entity |
| Predicate | englishShipsLost |
P821
|
FINISHED |
| Object | about 1 ship sunk |
—
|
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: about 1 ship sunk | Statement: [Battle of Lowestoft, englishShipsLost, about 1 ship sunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: englishShipsLost Context triple: [Battle of Lowestoft, englishShipsLost, about 1 ship sunk]
-
A.
shipsSunkOrTotalLoss
chosen
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
B.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
C.
navalVesselsAlliedApprox
Indicates that two or more naval vessels are approximately allied, suggesting a cooperative or friendly relationship without specifying a precise or formal alliance.
-
D.
battleshipsDamaged
Indicates that one or more battleships have sustained damage, typically as a result of combat or hostile action.
-
E.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.