Triple

T5172949
Position Surface form Disambiguated ID Type / Status
Subject Hakata Port E116728 entity
Predicate locatedIn P40 FINISHED
Object Fukuoka E38549 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: [Hakata Port, locatedIn, Fukuoka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fukuoka
Context triple: [Hakata Port, locatedIn, 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. 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.
  • D. Takamatsu
    Takamatsu is a coastal city in Japan’s Kagawa Prefecture on the island of Shikoku, known as a regional transport hub and gateway to the Seto Inland Sea.
  • E. Ōsaki
    Ōsaki is a major commercial and business district in Tokyo known for its high-rise office complexes and convenient rail connections.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd795252a481908634779f3f656574 completed March 20, 2026, 4:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69cc55bdf8c0819083b61987d70f21ca completed March 31, 2026, 11:16 p.m.
Created at: March 20, 2026, 1:45 p.m.