Triple

T552630
Position Surface form Disambiguated ID Type / Status
Subject Battle of Flamborough Head E11872 entity
Predicate primaryAdversaries P4675 FINISHED
Object USS Bonhomme Richard vs HMS Serapis 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: USS Bonhomme Richard vs HMS Serapis | Statement: [Battle of Flamborough Head, primaryAdversaries, USS Bonhomme Richard vs HMS Serapis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryAdversaries
Context triple: [Battle of Flamborough Head, primaryAdversaries, USS Bonhomme Richard vs HMS Serapis]
  • A. primaryEnemy chosen
    Indicates that one entity is the main or most significant adversary or opponent of another entity.
  • B. notableAdversary
    Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
  • C. primaryCompetition
    Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
  • D. targetsAsRacialEnemy
    Indicates that one party identifies and treats another party as an enemy specifically on the basis of their race.
  • E. opposingCommander
    Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
  • 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_69a4932941d08190815efd422f0b4ca7 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4991b296481908cf27e1d1ec67052 completed March 1, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69a494bae210819093c2e0d33a8ca51a completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.