Triple

T32841498
Position Surface form Disambiguated ID Type / Status
Subject HMS Bounty mutineers E839983 entity
Predicate someMembersCapturedBy P175531 FINISHED
Object HMS Pandora 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 Pandora | Statement: [HMS Bounty mutineers, someMembersCapturedBy, HMS Pandora]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: someMembersCapturedBy
Context triple: [HMS Bounty mutineers, someMembersCapturedBy, HMS Pandora]
  • A. capturedMembers
    Indicates that one party has taken members of another party into custody or control, typically by force or during a conflict or operation.
  • B. capturedFor
    Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
  • C. capturedBy
    Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
  • D. someMembersExhibit
    Indicates that within a group or collection, at least one member displays or possesses a specified property, behavior, or characteristic.
  • E. capturedIn
    Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another entity.
  • 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_69f3493ff0888190b51e974eae2a7834 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d210fc80819091ed8961aa2cddfb completed May 3, 2026, 4:41 a.m.
PD Predicate disambiguation batch_69f6cfe45554819089cbbd538d992132 completed May 3, 2026, 4:32 a.m.
PDg Predicate description generation batch_69f6d16b79dc8190ab0d4657f2ef9a5b completed May 3, 2026, 4:39 a.m.
Created at: May 1, 2026, 1:16 a.m.