Triple

T16689611
Position Surface form Disambiguated ID Type / Status
Subject Azabu E405559 entity
Predicate hasSubdistrict P747 FINISHED
Object Higashi-Azabu E916748 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: Higashi-Azabu | Statement: [Azabu, hasSubdistrict, Higashi-Azabu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Higashi-Azabu
Context triple: [Azabu, hasSubdistrict, Higashi-Azabu]
  • A. Nishi-Ogikubo
    Nishi-Ogikubo is a Tokyo neighborhood known for its laid-back residential atmosphere, vintage and antique shops, and small independent cafes and bars.
  • B. Minami-Aoyama
    Minami-Aoyama is an upscale district in Tokyo’s Minato ward known for its fashionable boutiques, stylish cafes, and contemporary art galleries.
  • C. Azabu area chosen
    The Azabu area is a central Tokyo neighborhood known for its upscale residential streets, international community, embassies, and proximity to Roppongi and other major districts.
  • D. Itabashi
    Itabashi is a special ward in northern Tokyo, Japan, known as a primarily residential area with a mix of traditional neighborhoods and modern urban infrastructure.
  • E. Akasaka
    Akasaka is a central Tokyo district known for its business centers, upscale hotels, and vibrant nightlife.
  • 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_69d8838c28748190b3f5967c743940ab completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37ea80d88819091fc61ed3c01955a completed April 18, 2026, 12:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009d32e7b48190b7dd4660bed4789d completed May 10, 2026, 2:58 p.m.
Created at: April 10, 2026, 5:19 a.m.