Triple

T24646327
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Kentish Knock (1652) E610119 entity
Predicate DutchFleetStrength P156898 FINISHED
Object about 62 ships 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 62 ships | Statement: [Battle of the Kentish Knock (1652), DutchFleetStrength, about 62 ships]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: DutchFleetStrength
Context triple: [Battle of the Kentish Knock (1652), DutchFleetStrength, about 62 ships]
  • A. fleetStrengthEnglish
    Indicates the relative military or naval power level associated with a fleet, expressed or categorized in English terms.
  • B. countryNavalForce
    Indicates that a country possesses, controls, or is associated with a particular naval military force.
  • C. embarkedForcesCapacity
    Indicates the maximum number of forces (e.g., troops or personnel) that can be embarked or carried by a given platform or unit.
  • D. navalForceComposition
    Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
  • E. dutchCasualties
    Indicates that the relationship specifies the number or occurrence of casualties suffered by Dutch entities in a given event or context.
  • 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.