Triple

T7265696
Position Surface form Disambiguated ID Type / Status
Subject 0 Series Shinkansen E159767 entity
Predicate serviceType P87 FINISHED
Object Hikari E306033 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: Hikari | Statement: [0 Series Shinkansen, serviceType, Hikari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hikari
Context triple: [0 Series Shinkansen, serviceType, Hikari]
  • A. Hikari chosen
    Hikari is a high-speed Shinkansen train service in Japan that operates on the Tokaido and Sanyo Shinkansen lines, offering fast intercity travel with fewer stops than local services.
  • B. Hoori
    Hoori is a deity in Japanese mythology, known as a divine hunter and ancestor of Japan’s imperial line.
  • C. Shinkiari
    Shinkiari is a town in Pakistan’s Khyber Pakhtunkhwa province, known for its agricultural surroundings and its location along the Karakoram Highway near Mansehra.
  • D. Katsuragi
    Katsuragi was a late-war Imperial Japanese Navy aircraft carrier that served in the Pacific Theater during World War II.
  • E. Katsuragi
    Katsuragi is a city in Japan known for its location in Nara Prefecture and its historical and cultural ties to the ancient Yamato region.
  • 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_69c68838f9948190875fd60b2351230c completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eae64e54819096b27c7b09060afa completed March 27, 2026, 8:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7d3cb62288190bac8da63c24fe076 completed March 28, 2026, 1:12 p.m.
Created at: March 27, 2026, 2:57 p.m.