Triple

T16564013
Position Surface form Disambiguated ID Type / Status
Subject Rokkō Airando E402409 entity
Predicate connectedBy P37 FINISHED
Object Rokkō Liner E363196 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: Rokkō Liner | Statement: [Rokkō Airando, connectedBy, Rokkō Liner]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rokkō Liner
Context triple: [Rokkō Airando, connectedBy, Rokkō Liner]
  • A. Rokkō Liner chosen
    Rokkō Liner is an automated guideway transit line in Kobe, Japan, connecting the artificial island of Rokkō Island with the mainland.
  • B. Keisei Skyliner
    Keisei Skyliner is a high-speed limited express train service in Japan that links central Tokyo with Narita International Airport.
  • C. Raichō limited express
    The Raichō limited express was a former Japanese limited express train service that operated mainly between Osaka and Kanazawa before being succeeded by the Thunderbird service.
  • D. Ariake limited express
    Ariake limited express is a Japanese limited express train service in Kyushu known for connecting major cities such as Fukuoka and Kumamoto.
  • E. Ryomo limited express
    The Ryomo limited express is a Japanese limited express train service providing fast, comfortable intercity travel on routes operated by Tobu Railway.
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3577043048190bc9bcf55069b769f completed April 18, 2026, 10:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00aae69d1481909f5514cc496f45b5 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:15 a.m.