Triple
T24646339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Kentish Knock (1652) |
E610119
|
entity |
| Predicate | EnglishFleetEffect |
P156899
|
FINISHED |
| Object | maintained cohesion and control |
—
|
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: maintained cohesion and control | Statement: [Battle of the Kentish Knock (1652), EnglishFleetEffect, maintained cohesion and control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishFleetEffect Context triple: [Battle of the Kentish Knock (1652), EnglishFleetEffect, maintained cohesion and control]
-
A.
fleetStrengthEnglish
Indicates the relative military or naval power level associated with a fleet, expressed or categorized in English terms.
-
B.
fleetCommander (British)
Indicates that the subject serves as the fleet commander for the British naval forces.
-
C.
EnglishFleetBase
Indicates a base or primary location associated with the English fleet in a given context.
-
D.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
E.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
- F. None of above. chosen
Provenance (4 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_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:33 a.m.