Triple

T19743612
Position Surface form Disambiguated ID Type / Status
Subject 対馬 E474193 entity
Predicate connectedByFerryTo P1831 FINISHED
Object 博多港 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: 博多港 | Statement: [対馬, connectedByFerryTo, 博多港]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 博多港
Context triple: [対馬, connectedByFerryTo, 博多港]
  • A. 熊本市
    熊本市 is the capital and largest city of Kumamoto Prefecture on Japan’s Kyushu island, known for its historic Kumamoto Castle and rich samurai-era heritage.
  • B. Hakata Port chosen
    Hakata Port is a major international seaport in Fukuoka, Japan, serving as a key gateway for passenger ferries and cargo between Kyushu, the rest of Japan, and East Asia.
  • C. Takamatsu Port
    Takamatsu Port is a major maritime hub in Japan’s Seto Inland Sea, serving as a key gateway for passenger ferries and cargo traffic connecting Shikoku with surrounding islands and mainland regions.
  • D. Port of Shimonoseki
    The Port of Shimonoseki is a major Japanese seaport and transportation hub on the western tip of Honshu, serving as a key gateway for domestic and international maritime traffic, including routes to Kyushu and South Korea.
  • E. 佐世保市
    佐世保市は、長崎県北部に位置し、米海軍基地やハウステンボスなどで知られる港湾工業都市です。
  • 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65162f0f88190b652fff01ee23090 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.