Triple

T16978668
Position Surface form Disambiguated ID Type / Status
Subject Tsukiji E411883 entity
Predicate near P350 FINISHED
Object Shinbashi 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: Shinbashi | Statement: [Tsukiji, near, Shinbashi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shinbashi
Context triple: [Tsukiji, near, Shinbashi]
  • A. Shinbashi chosen
    Shinbashi is a historic commercial and entertainment district in central Tokyo known as a major business hub and gateway between the Ginza area and the Shiodome skyscraper complex.
  • B. Shinagawa
    Shinagawa is a major commercial and transportation hub in Tokyo, Japan, known for its busy railway station, business districts, and waterfront developments.
  • C. Hamamatsucho
    Hamamatsucho is a central Tokyo district and major transportation hub known for its JR and monorail stations providing access to Haneda Airport and nearby business and waterfront areas.
  • D. Nihonbashi
    Nihonbashi is a historic commercial district in central Tokyo known for its iconic bridge, traditional merchants, and major financial and retail centers.
  • E. Kamitabashi
    Kamitabashi is a residential neighborhood located in the Kita ward of Tokyo, Japan.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d185a9408190a991bf8a1ef694f0 completed April 18, 2026, 6:46 p.m.
Created at: April 10, 2026, 5:32 a.m.