Triple

T3093038
Position Surface form Disambiguated ID Type / Status
Subject Yokohama Landmark Tower E64526 entity
Predicate view P2512 FINISHED
Object Yokohama city E10676 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: Yokohama city | Statement: [Yokohama Landmark Tower, view, Yokohama city]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yokohama city
Context triple: [Yokohama Landmark Tower, view, Yokohama city]
  • A. Yokohama chosen
    Yokohama is Japan’s second-largest city and a major international port located just south of Tokyo.
  • B. Nagoya
    Nagoya is a major industrial and commercial city in central Japan, known as a manufacturing hub and the capital of Aichi Prefecture.
  • C. Shibuya City
    Shibuya City is a major commercial and entertainment district in central Tokyo, Japan, famous for its bustling scramble crossing, youth culture, and fashion scene.
  • D. Bunkyō City
    Bunkyō City is a special ward in central Tokyo, Japan, known for its universities, historic temples, and quiet residential neighborhoods.
  • E. Chiba
    Chiba is a major city in Japan located east of Tokyo, known as the capital of Chiba Prefecture and a key commercial and residential hub in the Greater Tokyo Area.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada21055b88190b602425a513af7e6 completed March 8, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69beb0a5d4908190bb817c48cb485088 completed March 21, 2026, 2:52 p.m.
Created at: March 8, 2026, 3:03 p.m.