Triple

T37523001
Position Surface form Disambiguated ID Type / Status
Subject HMS Queen Charlotte (1790) E932829 entity
Predicate roleInBattleOfTheGloriousFirstOfJune P203867 FINISHED
Object flagship of Admiral Lord Howe 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: flagship of Admiral Lord Howe | Statement: [HMS Queen Charlotte (1790), roleInBattleOfTheGloriousFirstOfJune, flagship of Admiral Lord Howe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfTheGloriousFirstOfJune
Context triple: [HMS Queen Charlotte (1790), roleInBattleOfTheGloriousFirstOfJune, flagship of Admiral Lord Howe]
  • A. commanderAtGloriousFirstOfJune
    Indicates that an entity served as a commander during the naval battle known as the Glorious First of June.
  • B. roleInBattleOfTheChesapeake
    Indicates the specific function, position, or involvement an entity had in the Battle of the Chesapeake.
  • C. roleInBattleOfFlamboroughHead
    Indicates the specific role or involvement an entity had in the Battle of Flamborough Head.
  • D. roleInBattleOfSluys
    Indicates the specific role or involvement an entity had in the Battle of Sluys.
  • E. roleAtBattleOfToulon
    Indicates the specific role, position, or function an entity held during the Battle of Toulon.
  • F. None of above. chosen

Provenance (4 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_6a0227ce59a081909fe1ba1181d86b4d completed May 11, 2026, 7:02 p.m.
PD Predicate disambiguation batch_6a02273989208190beb948b8c7bdaee3 completed May 11, 2026, 7 p.m.
PDg Predicate description generation batch_6a0227cd6e348190983e90e349aa155b completed May 11, 2026, 7:02 p.m.
Created at: May 3, 2026, 4:17 p.m.