Triple

T17845800
Position Surface form Disambiguated ID Type / Status
Subject Nagasaki Main Line E445655 entity
Predicate connectsCity P4245 FINISHED
Object Fukuoka 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: Fukuoka | Statement: [Nagasaki Main Line, connectsCity, Fukuoka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fukuoka
Context triple: [Nagasaki Main Line, connectsCity, Fukuoka]
  • A. Fukuoka chosen
    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
    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 (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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffa4c648190a88a4b0733493d91 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.