Triple

T16239513
Position Surface form Disambiguated ID Type / Status
Subject Omotesando Station E394203 entity
Predicate locatedUnder P10157 FINISHED
Object Aoyama-dori E323146 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: Aoyama-dori | Statement: [Omotesando Station, locatedUnder, Aoyama-dori]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aoyama-dori
Context triple: [Omotesando Station, locatedUnder, Aoyama-dori]
  • A. Aoyama-dori chosen
    Aoyama-dori is a major thoroughfare in Tokyo’s Aoyama district, known for its upscale boutiques, modern architecture, and cultural landmarks.
  • B. Karasuma-dori
    Karasuma-dori is a major north–south avenue in Kyoto, Japan, known as one of the city’s primary business and transportation corridors.
  • C. Yamate-dori
    Yamate-dori is a major arterial ring road in Tokyo, Japan, running north–south and connecting numerous key districts and highways across the city.
  • D. Waseda-dori
    Waseda-dori is a major urban street in Tokyo, Japan, running through the Waseda area and serving as an important local thoroughfare.
  • E. Hakusan-dori
    Hakusan-dori is a major urban street in Tokyo, Japan, known for connecting several central neighborhoods and serving as an important traffic and commercial artery.
  • 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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2455d5270819090171d4207223a28 completed April 17, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0025f740ec8190ab075c953e27cfba completed May 10, 2026, 6:30 a.m.
Created at: April 10, 2026, 5:04 a.m.