Triple

T11240978
Position Surface form Disambiguated ID Type / Status
Subject Battle of the River Plate E266071 entity
Predicate involvedShip P862 FINISHED
Object HMS Ajax E52191 NE 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: HMS Ajax | Statement: [Battle of the River Plate, involvedShip, HMS Ajax]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HMS Ajax
Context triple: [Battle of the River Plate, involvedShip, HMS Ajax]
  • A. HMS Ajax chosen
    HMS Ajax was a British Leander-class light cruiser of the Royal Navy that gained fame for its role in early World War II naval actions, particularly in the South Atlantic.
  • B. HMS Ajax
    HMS Ajax was a British Royal Navy warship that served as part of the King George V-class of battleships during the mid-20th century.
  • C. HMS Valiant
    HMS Valiant was a British Royal Navy nuclear-powered fleet submarine of the Valiant class that served during the Cold War.
  • D. HMS Valiant
    HMS Valiant is a planned Royal Navy nuclear-powered ballistic missile submarine intended to serve as part of the United Kingdom’s next-generation strategic deterrent force.
  • E. HMS Ardent
    HMS Ardent was a Royal Navy Type 21 frigate that gained prominence for her role and sinking during the Falklands War in 1982.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e919eaf48190a1457851cfc56afb completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f416d18eec81909f417e49507b117d completed May 1, 2026, 2:58 a.m.
Created at: April 8, 2026, 9:30 p.m.