Triple

T23085132
Position Surface form Disambiguated ID Type / Status
Subject George Sullivan E575576 entity
Predicate shipSunkBy P4687 FINISHED
Object Japanese submarine I-26 NE NERFINISHED

How this triple was built (4 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: Japanese submarine I-26 | Statement: [George Sullivan, shipSunkBy, Japanese submarine I-26]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Japanese submarine I-26
Context triple: [George Sullivan, shipSunkBy, Japanese submarine I-26]
  • A. Japanese submarine I-168
    Japanese submarine I-168 was an Imperial Japanese Navy fleet submarine best known for its role in the Battle of Midway, where it torpedoed and sank the damaged aircraft carrier USS Yorktown and the destroyer USS Hammann.
  • B. Japanese submarine I-58
    Japanese submarine I-58 was an Imperial Japanese Navy B3 type cruiser submarine best known for torpedoing and sinking the USS Indianapolis near the end of World War II.
  • C. Japanese submarine RO-108
    Japanese submarine RO-108 was an Imperial Japanese Navy Ro-100-class coastal submarine that operated in the Pacific during World War II.
  • D. Japanese destroyer Suzukaze
    Japanese destroyer Suzukaze was an Imperial Japanese Navy Shiratsuyu-class destroyer that served actively in World War II, particularly in the Solomon Islands campaign.
  • E. Japanese destroyer Oshio
    The Japanese destroyer Oshio was an Imperial Japanese Navy Asashio-class destroyer that saw extensive service in the early Pacific War, including major actions in the Netherlands East Indies campaign.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Japanese submarine I-26
Target entity description: Japanese submarine I-26 was an Imperial Japanese Navy Type B1 long-range fleet submarine active in the Pacific during World War II, known for sinking several Allied ships.
  • A. Japanese submarine I-168
    Japanese submarine I-168 was an Imperial Japanese Navy fleet submarine best known for its role in the Battle of Midway, where it torpedoed and sank the damaged aircraft carrier USS Yorktown and the destroyer USS Hammann.
  • B. Japanese submarine I-58
    Japanese submarine I-58 was an Imperial Japanese Navy B3 type cruiser submarine best known for torpedoing and sinking the USS Indianapolis near the end of World War II.
  • C. Japanese submarine RO-108
    Japanese submarine RO-108 was an Imperial Japanese Navy Ro-100-class coastal submarine that operated in the Pacific during World War II.
  • D. Japanese destroyer Suzukaze
    Japanese destroyer Suzukaze was an Imperial Japanese Navy Shiratsuyu-class destroyer that served actively in World War II, particularly in the Solomon Islands campaign.
  • E. Japanese destroyer Oshio
    The Japanese destroyer Oshio was an Imperial Japanese Navy Asashio-class destroyer that saw extensive service in the early Pacific War, including major actions in the Netherlands East Indies campaign.
  • F. None of above. chosen
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shipSunkBy
Context triple: [George Sullivan, shipSunkBy, Japanese submarine I-26]
  • A. sunkBy chosen
    Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
  • B. shipTypeSunk
    Indicates that a particular type of ship has been sunk as a result of some event or action.
  • C. wasSunkAs
    Indicates that an entity met its end by being sunk in a specified role, context, or capacity.
  • D. shipAttacked
    Indicates that one ship has carried out an attack against another ship.
  • E. shipsSunkOrTotalLoss
    Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da3d4208190b7bfd1026e773dbf completed April 29, 2026, 4:48 a.m.
PD Predicate disambiguation batch_69ef89e5ce748190b2c3ac3843484127 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 3:57 p.m.