Triple

T36196858
Position Surface form Disambiguated ID Type / Status
Subject Battle between USS Constitution and HMS Java E1047150 entity
Predicate capturedShipFate P152819 FINISHED
Object HMS Java burned and sunk after battle 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 Java burned and sunk after battle | Statement: [Battle between USS Constitution and HMS Java, capturedShipFate, HMS Java burned and sunk after battle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: capturedShipFate
Context triple: [Battle between USS Constitution and HMS Java, capturedShipFate, HMS Java burned and sunk after battle]
  • A. capturedShip
    Indicates that one party has taken control of another party's ship, typically by force or seizure.
  • B. capturedShipType
    Indicates that one entity has taken possession of another entity’s ship, specifying the type or category of the ship that was captured.
  • C. shipSankIn
    Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
  • D. fateOfDesignatedShip chosen
    Indicates the outcome or final status that befalls a specifically designated ship.
  • E. dispositionOfShips
    Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
  • 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_69f76e414bdc8190996f15a544220a3d completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b69b333081909cadbed3fcb8ecf5 completed May 3, 2026, 8:56 p.m.
PD Predicate disambiguation batch_69f7b4c2a5f8819094ad4621d7b97e0c completed May 3, 2026, 8:49 p.m.
Created at: May 3, 2026, 4:08 p.m.