Triple

T37522953
Position Surface form Disambiguated ID Type / Status
Subject HMS Royal Sovereign (1786) E932828 entity
Predicate commandingOfficerAtTrafalgar P45997 FINISHED
Object Vice-Admiral Cuthbert Collingwood 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: Vice-Admiral Cuthbert Collingwood | Statement: [HMS Royal Sovereign (1786), commandingOfficerAtTrafalgar, Vice-Admiral Cuthbert Collingwood]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commandingOfficerAtTrafalgar
Context triple: [HMS Royal Sovereign (1786), commandingOfficerAtTrafalgar, Vice-Admiral Cuthbert Collingwood]
  • A. opponentAtTrafalgar
    Indicates that one entity was an opposing side or adversary of the other in the Battle of Trafalgar.
  • B. roleAtTrafalgar chosen
    Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
  • C. notableNavalCommander
    Indicates that the subject is recognized as a distinguished or historically significant commander in naval forces.
  • D. admiralOfFleet
    Indicates a relationship where a person holds the highest naval rank or command position over an entire fleet.
  • E. navalCommanderAtBattleOfNavarino
    Indicates that a person served as a naval commander participating in the Battle of Navarino.
  • F. None of above.

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_69f76ec8862c8190bfa24145f5480642 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fdd92396788190ae1424bc1ae55844 completed May 8, 2026, 12:37 p.m.
PD Predicate disambiguation batch_69fdd678f40481909a717a2daec83b36 completed May 8, 2026, 12:26 p.m.
Created at: May 3, 2026, 4:17 p.m.