Triple

T6129723
Position Surface form Disambiguated ID Type / Status
Subject Takarazuka E136682 entity
Predicate locatedNear P294 FINISHED
Object Kobe E3089 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: Kobe | Statement: [Takarazuka, locatedNear, Kobe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kobe
Context triple: [Takarazuka, locatedNear, Kobe]
  • A. Kobe chosen
    Kobe is a major port city in Japan’s Kansai region, known for its scenic harbor setting, cosmopolitan atmosphere, and famous Kobe beef.
  • B. Kobe Nankinmachi
    Kobe Nankinmachi is a famous Chinatown district in Kobe, Japan, known for its Chinese restaurants, shops, and vibrant cultural festivals.
  • C. Kobe, Hyogo, Japan
    Kobe, Hyogo, Japan is a major port city in western Japan known for its international trade, scenic harbor setting between mountains and sea, and famous Kobe beef.
  • D. Kobe waterfront redevelopment area
    The Kobe waterfront redevelopment area is a revitalized coastal district in Kobe, Japan, featuring parks, cultural attractions, and commercial facilities that showcase the city’s modern harborfront.
  • E. Nada-ku, Kobe
    Nada-ku, Kobe is a ward of Kobe, Japan, known for its scenic Mount Rokko area, sake breweries, and residential neighborhoods.
  • 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_69c008a0a37c81908e5b4f879158afb3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05c4c8570819096dc87f0de2a9887 completed March 22, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c14143bf008190ba804ae094ffb71c completed March 23, 2026, 1:33 p.m.
Created at: March 22, 2026, 4:15 p.m.