Triple

T21385850
Position Surface form Disambiguated ID Type / Status
Subject Aoyama, Tokyo E527494 entity
Predicate adjacentTo P224 FINISHED
Object Omotesandō 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: Omotesandō | Statement: [Aoyama, Tokyo, adjacentTo, Omotesandō]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Omotesandō
Context triple: [Aoyama, Tokyo, adjacentTo, Omotesandō]
  • A. Omotesandō chosen
    Omotesandō is a fashionable, tree-lined avenue in Tokyo known for its high-end boutiques, modern architecture, and trendy cafés.
  • B. Sakuragaokacho
    Sakuragaokacho is a neighborhood in Tokyo’s Shibuya ward known for its urban atmosphere and proximity to Shibuya Station.
  • C. Komagome
    Komagome is a residential and commercial neighborhood in Tokyo known for its traditional atmosphere, historic temples, and the renowned Rikugien Garden.
  • D. Nagatacho
    Nagatacho is a central district in Tokyo, Japan, known as the political heart of the country and home to key government institutions such as the National Diet Building.
  • E. Nishi-Tobecho
    Nishi-Tobecho is a notable neighborhood within Nishi Ward in Yokohama, Japan, known as part of the city’s central urban area.
  • 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_69e0b51f363c8190944000ab5523b02b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0f3d37c8190b43ec77cdb1904c8 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:12 p.m.