Triple

T13037670
Position Surface form Disambiguated ID Type / Status
Subject Sanyō Shinkansen E326605 entity
Predicate connectsCity P4245 FINISHED
Object Fukuoka E691976 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: Fukuoka | Statement: [Sanyō Shinkansen, connectsCity, Fukuoka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fukuoka
Context triple: [Sanyō Shinkansen, connectsCity, Fukuoka]
  • A. Fukuoka
    Fukuoka is a major Japanese city on the northern shore of Kyushu, known as an important economic, cultural, and transportation hub with a busy international port.
  • B. Kitakyushu
    Kitakyushu is a major industrial and port city located in Fukuoka Prefecture on Japan’s Kyushu island.
  • C. Fukuoka Jisho
    Fukuoka Jisho is a Japanese real estate development company best known for creating large-scale urban complexes such as Canal City Hakata in Fukuoka.
  • D. Shimonoseki City chosen
    Shimonoseki City is a coastal city in Yamaguchi Prefecture, Japan, known as a major gateway between Honshu and Kyushu and for its historic role in maritime trade and the First Sino-Japanese War.
  • E. Toyoake
    Toyoake is a city in central Japan known for its residential communities and proximity to the Nagoya metropolitan area in Aichi Prefecture.
  • 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_69d8076cc45c81908123123f43e69266 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d9804b743c8190810dc5c14bc6d912 completed April 10, 2026, 10:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69f71f03e00c819091ae5273aa10fe4b completed May 3, 2026, 10:10 a.m.
Created at: April 9, 2026, 8:55 p.m.