Triple

T8725745
Position Surface form Disambiguated ID Type / Status
Subject Kawanishi N1K E207126 entity
Predicate instanceOf P0 FINISHED
Object Japanese Navy aircraft C24977 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Japanese Navy aircraft
Context triple: [Kawanishi N1K, instanceOf, Japanese Navy aircraft]
  • A. Japan Air Self-Defense Force unit
    A Japan Air Self-Defense Force unit is an organizational entity within Japan’s air defense branch, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions.
  • B. Japanese torpedo
    A Japanese torpedo is a self-propelled underwater weapon developed and used by Japan, particularly notable in World War II for its advanced design, long range, and high speed in attacking enemy ships.
  • C. Imperial Japanese Navy institution
    An Imperial Japanese Navy institution is an organized body, such as a naval academy, staff college, research bureau, or administrative office, that supported the training, planning, governance, and operational effectiveness of the Imperial Japanese Navy.
  • D. Japanese naval task force
    A Japanese naval task force is an organized, mission-focused grouping of Japanese warships, aircraft, and support vessels operating together under a unified command to achieve specific maritime objectives.
  • E. Imperial Japanese Navy warship
    An Imperial Japanese Navy warship is a naval combat vessel that served under Japan’s maritime military forces, primarily during the late 19th and early 20th centuries, designed and equipped for roles such as fleet engagement, escort, and power projection.
  • F. None of above. chosen

Provenance (1 batch)

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_69ca835811d8819081ea00fd2a2c9a1c completed March 30, 2026, 2:06 p.m.
Created at: March 30, 2026, 6:36 p.m.