Triple

T12632172
Position Surface form Disambiguated ID Type / Status
Subject Takadanobaba E301669 entity
Predicate hasMainRoad P385 FINISHED
Object Waseda-dori E945233 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: Waseda-dori | Statement: [Takadanobaba, hasMainRoad, Waseda-dori]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waseda-dori
Context triple: [Takadanobaba, hasMainRoad, Waseda-dori]
  • A. Waseda-dori chosen
    Waseda-dori is a major urban street in Tokyo, Japan, running through the Waseda area and serving as an important local thoroughfare.
  • B. Aoyama-dori
    Aoyama-dori is a major thoroughfare in Tokyo’s Aoyama district, known for its upscale boutiques, modern architecture, and cultural landmarks.
  • 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. Kokusai-dori
    Kokusai-dori is Naha’s main bustling shopping and entertainment street, famous for its shops, restaurants, and vibrant nightlife in Okinawa, Japan.
  • E. Hibiya-dori
    Hibiya-dori is a major thoroughfare in central Tokyo, Japan, running through key business and government districts near the Imperial Palace.
  • 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_69d7bdec9f9c8190b4bac675b7588211 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9610e4f408190946f37325d69375c completed April 10, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f66871998c8190af8bd3f9ec596ada completed May 2, 2026, 9:11 p.m.
Created at: April 9, 2026, 5:15 p.m.