Triple

T18496193
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Dome Corporation E451954 entity
Predicate locatedIn P40 FINISHED
Object Tokyo, Japan 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: Tokyo, Japan | Statement: [Tokyo Dome Corporation, locatedIn, Tokyo, Japan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tokyo, Japan
Context triple: [Tokyo Dome Corporation, locatedIn, 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. Tokio
    Tokio is a popular asynchronous runtime for the Rust programming language, providing event-driven, non-blocking I/O for building high-performance network and concurrent applications.
  • D. Ō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.
  • E. 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.
  • 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_69d8d3855d50819097fc8561b0299dd9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e532c09a8081909cf0b44df3682bb8 completed April 19, 2026, 7:53 p.m.
Created at: April 10, 2026, 11:35 a.m.