Triple

T16984359
Position Surface form Disambiguated ID Type / Status
Subject Biwa-ko Line E412024 entity
Predicate connects P390 FINISHED
Object Kusatsu 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: Kusatsu | Statement: [Biwa-ko Line, connects, Kusatsu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kusatsu
Context triple: [Biwa-ko Line, connects, Kusatsu]
  • A. Kusatsu chosen
    Kusatsu is a Japanese city in Shiga Prefecture known as a regional commercial hub and transportation crossroads near Lake Biwa.
  • B. Shiraoi
    Shiraoi is a coastal town in Hokkaido, Japan, known for its Ainu cultural heritage and natural hot springs.
  • C. Noshiro
    Noshiro is a coastal city in northern Japan known for its port on the Sea of Japan and its forestry and basketball traditions.
  • D. Fujikawaguchiko
    Fujikawaguchiko is a Japanese resort town in Yamanashi Prefecture known for its views of Mount Fuji and Lake Kawaguchi, hot springs, and access to Fuji Five Lakes.
  • E. Semboku
    Semboku is a city in Akita Prefecture, Japan, known for its historic samurai district in Kakunodate and scenic Lake Tazawa.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d18a0bf881908c449f499eb86495 completed April 18, 2026, 6:46 p.m.
Created at: April 10, 2026, 5:32 a.m.