Triple

T1337182
Position Surface form Disambiguated ID Type / Status
Subject Gwangju E28778 entity
Predicate sisterCity P1072 FINISHED
Object Sendai E40916 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: Sendai | Statement: [Gwangju, sisterCity, Sendai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sendai
Context triple: [Gwangju, sisterCity, Sendai]
  • A. Sendai chosen
    Sendai is the largest city in Japan’s Tōhoku region, known for its lush greenery, historic sites, and status as a major economic and cultural center in northeastern Honshu.
  • B. Yokohama
    Yokohama is Japan’s second-largest city and a major international port located just south of Tokyo.
  • C. Morioka
    Morioka is the capital city of Iwate Prefecture in Japan’s Tōhoku region, known for its historic castle site, surrounding mountains, and distinctive local noodle dishes.
  • D. 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.
  • E. Nagoya
    Nagoya is a major industrial and commercial city in central Japan, known as a manufacturing hub and the capital of 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_69a498561a508190a3e1bc137c2b866a completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1edda1c81909a1149b254b0d57e completed March 1, 2026, 10:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1eebcf8e88190b657a55348f6870e completed March 11, 2026, 10:37 p.m.
Created at: March 1, 2026, 7:55 p.m.