Triple

T23119015
Position Surface form Disambiguated ID Type / Status
Subject Task Force 57 E576837 entity
Predicate headquartersShip P35755 FINISHED
Object HMS Howe NE NERFINISHED

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: HMS Howe | Statement: [Task Force 57, headquartersShip, HMS Howe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HMS Howe
Context triple: [Task Force 57, headquartersShip, HMS Howe]
  • A. HMS Howe chosen
    HMS Howe was a British King George V-class battleship that served prominently with the Royal Navy during World War II, including operations in the Atlantic and Pacific theaters.
  • B. HMS Hawke
    HMS Hawke was a British Royal Navy Edgar-class protected cruiser best known for its 1911 collision with the ocean liner RMS Olympic.
  • C. HMS Havock
    HMS Havock was an H-class Royal Navy destroyer that saw active service in the Mediterranean during the early years of World War II.
  • D. HMS Hunter
    HMS Hunter was a British prison ship notorious for holding American prisoners of war in brutal conditions during the American Revolutionary War.
  • E. HMS Hogue
    HMS Hogue was a British Cressy-class armored cruiser of the Royal Navy that served in the early 20th century and was sunk during World War I in the North Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245f6c2e881909a228fdcfeb7c7d3 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e4ece5481908d05b4b1e6a07db3 completed April 29, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:59 p.m.