Triple

T16851719
Position Surface form Disambiguated ID Type / Status
Subject Ichigo Offensive E409690 entity
Predicate alsoKnownAs P39 FINISHED
Object Ichi-Go E409687 NE FINISHED

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: Ichi-Go | Statement: [Ichigo Offensive, alsoKnownAs, Ichi-Go]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ichi-Go
Context triple: [Ichigo Offensive, alsoKnownAs, Ichi-Go]
  • A. Ichi-Go chosen
    Ichi-Go was the Japanese codename for a major 1944 World War II military offensive in China aimed at securing railways and airfields from Chinese and Allied forces.
  • B. Kakushōkaku
    Kakushōkaku is a historic Japanese-style residence located within Yokohama’s Sankeien Garden, known for its traditional architecture and scenic views over the landscaped grounds.
  • C. Ishin
    Ishin is the common abbreviated name for Nippon Ishin no Kai, a Japanese political party known for its reformist and regionalist agenda.
  • D. Ten-Go
    Ten-Go was the codename for Japan’s final major naval operation in World War II, centered on the battleship Yamato’s doomed sortie toward Okinawa in April 1945.
  • E. Tenchō
    Tenchō was a Japanese era name (nengō) of the early Heian period, used during the reign of Emperor Junna.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b379b8fc81908d8bc9950c7f8bad completed April 18, 2026, 4:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c2a6f2c48190874839f78f943fdb completed May 10, 2026, 5:38 p.m.
Created at: April 10, 2026, 5:24 a.m.