Triple

T14831921
Position Surface form Disambiguated ID Type / Status
Subject Akashi Strait E348727 entity
Predicate locatedBetween P1262 FINISHED
Object Kobe E499546 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: [Akashi Strait, locatedBetween, Kobe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kobe
Context triple: [Akashi Strait, locatedBetween, Kobe]
  • A. Kobe
    Kobe is a major port city in Japan’s Kansai region, known for its scenic harbor setting, cosmopolitan atmosphere, and famous Kobe beef.
  • B. Neo Kobe City
    Neo Kobe City is a futuristic, cyberpunk metropolis shrouded in perpetual rain and noir atmosphere, serving as the primary backdrop for Hideo Kojima’s adventure game Snatcher.
  • C. Kobe Nankinmachi
    Kobe Nankinmachi is a famous Chinatown district in Kobe, Japan, known for its Chinese restaurants, shops, and vibrant cultural festivals.
  • D. Kobe – Naha
    Kobe – Naha is a domestic air route in Japan connecting Kobe in Hyōgo Prefecture with Naha in Okinawa Prefecture.
  • E. Kobe, Hyogo, Japan chosen
    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.
  • 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_69d822ec69008190a9232caa68836872 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded0748eec8190a39c94024c3a3e3e completed April 14, 2026, 11:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe38a393988190837fdca148f4058c completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:52 a.m.