Triple

T21672096
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cape St. Vincent (1780) E534873 entity
Predicate commandRank (George Brydges Rodney) P30999 FINISHED
Object Admiral 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: Admiral | Statement: [Battle of Cape St. Vincent (1780), commandRank (George Brydges Rodney), Admiral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commandRank (George Brydges Rodney)
Context triple: [Battle of Cape St. Vincent (1780), commandRank (George Brydges Rodney), Admiral]
  • A. navalRankContext
    Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
  • B. commandingOfficerRank
    Indicates the military rank held by the officer who has command authority over a given individual or unit.
  • C. hasCommanderRank chosen
    Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
  • D. commanderInChiefRank
    Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
  • E. fleetCommander (British)
    Indicates that the subject serves as the fleet commander for the British naval forces.
  • 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_69e0c46898008190aa618a4af55bd1ee completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef8a0cd7648190b9981393f0b2bee9 completed April 27, 2026, 4:08 p.m.
PD Predicate disambiguation batch_69e6968abfdc81909cf9e0bd72db9eca completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:39 p.m.