Triple

T15919090
Position Surface form Disambiguated ID Type / Status
Subject Kengo Kuma E386044 entity
Predicate basedIn P40 FINISHED
Object Tokyo, Japan E5560 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: Tokyo, Japan | Statement: [Kengo Kuma, basedIn, Tokyo, Japan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tokyo, Japan
Context triple: [Kengo Kuma, basedIn, Tokyo, Japan]
  • A. Tokyo chosen
    Tokyo is Japan’s largest metropolis and a global center of finance, culture, technology, and transportation.
  • B. Tokyo
    "Tokyo" is a popular Afrobeats song by Ghanaian singer King Promise featuring Nigerian artist Wizkid.
  • C. Ōta, Tokyo
    Ōta, Tokyo is a large ward in southern Tokyo known for its mix of residential and industrial areas and for hosting Haneda Airport, one of Japan’s major international gateways.
  • D. Tōkyō-wan
    Tōkyō-wan is the Japanese name for Tokyo Bay, a major urban bay on the Pacific coast of Honshu that serves as a key economic and transportation hub for the Greater Tokyo Area.
  • E. Chuo City, Tokyo
    Chuo City, Tokyo is a central ward of Tokyo known for its historic commercial districts like Nihonbashi and Ginza, serving as a major hub for finance, retail, and culture.
  • 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_69d86da686e4819097cbf3b1fc2d881d completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1567ff9e48190b73cb101fc3f7b2b completed April 16, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0180bd1e5c8190a6a96581ce8a37de completed May 11, 2026, 7:09 a.m.
Created at: April 10, 2026, 4:52 a.m.