Triple

T17318531
Position Surface form Disambiguated ID Type / Status
Subject Fuji-class battleship E420494 entity
Predicate hasMember P10 FINISHED
Object Japanese battleship Yashima NE NERFINISHED

How this triple was built (3 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 battleship Yashima | Statement: [Fuji-class battleship, hasMember, Japanese battleship Yashima]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Japanese battleship Yashima
Context triple: [Fuji-class battleship, hasMember, Japanese battleship Yashima]
  • A. Japanese battleship Shikishima
    Japanese battleship Shikishima was a pre-dreadnought warship of the Imperial Japanese Navy that played a significant role in the Russo-Japanese War, including major fleet engagements.
  • B. Japanese battleship Tosa
    Japanese battleship Tosa was a planned but never completed Imperial Japanese Navy battleship of the Tosa class, intended to be a powerful capital ship in the early 1920s before being cancelled under naval disarmament treaties.
  • C. IJN battleship Yamashiro
    IJN battleship Yamashiro was a Japanese Fuso-class dreadnought battleship that served in the Imperial Japanese Navy and was sunk during the Battle of Surigao Strait in World War II.
  • D. Japanese battleship Suwo
    Japanese battleship Suwo was a pre-dreadnought battleship of the Imperial Japanese Navy, originally built for the Imperial Russian Navy as Pobeda and captured and reused by Japan after the Russo-Japanese War.
  • E. Japanese battleship Hiei
    Japanese battleship Hiei was a Kongō-class fast battleship of the Imperial Japanese Navy that saw extensive action in the Pacific during World War II before being sunk in 1942.
  • 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 battleship Yashima
Target entity description: Japanese battleship Yashima was a pre-dreadnought warship of the Imperial Japanese Navy that served in the Russo-Japanese War before sinking after striking mines in 1904.
  • A. Japanese battleship Shikishima
    Japanese battleship Shikishima was a pre-dreadnought warship of the Imperial Japanese Navy that played a significant role in the Russo-Japanese War, including major fleet engagements.
  • B. Japanese battleship Tosa
    Japanese battleship Tosa was a planned but never completed Imperial Japanese Navy battleship of the Tosa class, intended to be a powerful capital ship in the early 1920s before being cancelled under naval disarmament treaties.
  • C. IJN battleship Yamashiro
    IJN battleship Yamashiro was a Japanese Fuso-class dreadnought battleship that served in the Imperial Japanese Navy and was sunk during the Battle of Surigao Strait in World War II.
  • D. Japanese battleship Suwo
    Japanese battleship Suwo was a pre-dreadnought battleship of the Imperial Japanese Navy, originally built for the Imperial Russian Navy as Pobeda and captured and reused by Japan after the Russo-Japanese War.
  • E. Japanese battleship Hiei
    Japanese battleship Hiei was a Kongō-class fast battleship of the Imperial Japanese Navy that saw extensive action in the Pacific during World War II before being sunk in 1942.
  • F. None of above. chosen

Provenance (2 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4399f84a881908dd99ecd7cc02708 completed April 19, 2026, 2:10 a.m.
Created at: April 10, 2026, 5:43 a.m.