Triple

T17580887
Position Surface form Disambiguated ID Type / Status
Subject Battle of Yashima E428199 entity
Predicate location P40 FINISHED
Object Yashima 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: Yashima | Statement: [Battle of Yashima, location, Yashima]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yashima
Context triple: [Battle of Yashima, location, Yashima]
  • A. Yashima
    Yashima was a former municipality in Akita Prefecture, Japan, that later became part of the city of Yurihonjō through a municipal merger.
  • B. Yashima chosen
    Yashima is a historic plateau and former island in Takamatsu, Kagawa Prefecture, known for its panoramic views of the Seto Inland Sea and as a key battlefield of the Genpei War.
  • C. Himejima
    Himejima is one of the small islands in Tokyo’s Mukojima Islands group, known for its remote, natural setting in the Pacific.
  • D. Iōjima
    Iōjima, more widely known as Iwo Jima, is a small volcanic island in the Pacific Ocean famous as the site of a major World War II battle between Japan and the United States.
  • E. Tsukishima
    Tsukishima is a man-made island and residential district in Tokyo’s Chūō ward, known for its high-rise apartments and famous monjayaki restaurants.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e463cdb1608190a7e249ad6531b1dc completed April 19, 2026, 5:10 a.m.
Created at: April 10, 2026, 5:50 a.m.