Triple

T105780
Position Surface form Disambiguated ID Type / Status
Subject Japan Standard Time E2133 entity
Predicate usedByRegion P908 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: [Japan Standard Time, usedByRegion, Fukuoka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fukuoka
Context triple: [Japan Standard Time, usedByRegion, 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. Niigata
    Niigata is a major coastal city in north-central Japan known for its important seaport on the Sea of Japan, rice production, and sake brewing.
  • C. Nagoya
    Nagoya is a major industrial and commercial city in central Japan, known as a manufacturing hub and the capital of Aichi Prefecture.
  • D. Yokohama
    Yokohama is Japan’s second-largest city and a major international port located just south of Tokyo.
  • E. Osaka
    Osaka is Japan's third-largest city and a major economic, cultural, and historical hub known for its vibrant street food, bustling nightlife, and role as a commercial center in the Kansai region.
  • 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_69a24e0a5b7c81908d52da08c60dabc4 completed Feb. 28, 2026, 2:08 a.m.
NER Named-entity recognition batch_69a25b7e2c188190b1dd8aafd4507a99 completed Feb. 28, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3c40fb3c88190818cc5c2560b1253 completed March 1, 2026, 4:43 a.m.
Created at: Feb. 28, 2026, 2:12 a.m.