Triple

T29847759
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Kentish Knock E757975 entity
Predicate dutchShipsOfTheLine P167663 FINISHED
Object about 8 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 8 | Statement: [Battle of the Kentish Knock, dutchShipsOfTheLine, about 8]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dutchShipsOfTheLine
Context triple: [Battle of the Kentish Knock, dutchShipsOfTheLine, about 8]
  • A. shipsOfTheLine
    Indicates a relationship where the associated entities are classified as ships of the line, i.e., major warships designed to participate in the main line of battle.
  • B. BritishShipsOfTheLine
    Indicates a relationship where the subject is classified as a ship of the line that belonged to or was operated by Britain.
  • C. FrenchShips
    Indicates that the ships involved are associated with France, typically by nationality, registration, or operation under the French flag.
  • D. DutchFleetStrength
    Indicates the relative size or power of the Dutch fleet in a given context or time period.
  • E. FrenchShipsOfTheLineEngaged
    Indicates that French ships of the line were actively involved in a naval engagement or battle.
  • 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_69f2245a82cc8190a387e7d0118d710b completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f6764489c881909618ff635fe6c410 completed May 2, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69f66ac32b60819092290b2de35988d3 completed May 2, 2026, 9:21 p.m.
PDg Predicate description generation batch_69f66bd123108190b451eb6e23842adb completed May 2, 2026, 9:25 p.m.
Created at: April 29, 2026, 5:42 p.m.