Triple

T18892698
Position Surface form Disambiguated ID Type / Status
Subject Town of Ajax E462130 entity
Predicate namedAfter P63 FINISHED
Object HMS Ajax 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 Ajax | Statement: [Town of Ajax, namedAfter, HMS Ajax]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HMS Ajax
Context triple: [Town of Ajax, namedAfter, HMS Ajax]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. HMS Valiant
    HMS Valiant was a prominent Royal Navy warship that served in several major 18th-century naval engagements, including actions during the Seven Years' War and the American Revolutionary War.
  • E. HMS Valiant
    HMS Valiant was a Queen Elizabeth-class British battleship that served prominently in both World Wars, particularly in Mediterranean naval operations.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c47bbf908190b141e98e3468e908 completed April 20, 2026, 6:15 a.m.
Created at: April 10, 2026, 11:58 a.m.