Triple
T24646338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Kentish Knock (1652) |
E610119
|
entity |
| Predicate | DutchFleetEffect |
P27109
|
FINISHED |
| Object | several ships damaged or 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 damaged or lost | Statement: [Battle of the Kentish Knock (1652), DutchFleetEffect, several ships damaged or lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchFleetEffect Context triple: [Battle of the Kentish Knock (1652), DutchFleetEffect, several ships damaged or lost]
-
A.
DutchFleetStrength
Indicates the relative size or power of the Dutch fleet in a given context or time period.
-
B.
effectOnDutchRepublic
chosen
Indicates the impact or consequences that something has on the Dutch Republic.
-
C.
EnglishFleetEffect
Indicates the impact or influence exerted by the English fleet on another entity, situation, or outcome.
-
D.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
E.
DutchSide
Indicates that one entity is located on, associated with, or belongs to the Dutch side of a border, region, or divided area in relation to another 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:33 a.m.