Triple

T14724600
Position Surface form Disambiguated ID Type / Status
Subject Series E7 Shinkansen E345904 entity
Predicate usedOnService P2367 FINISHED
Object Hakutaka E756181 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: Hakutaka | Statement: [Series E7 Shinkansen, usedOnService, Hakutaka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hakutaka
Context triple: [Series E7 Shinkansen, usedOnService, Hakutaka]
  • A. Hakutaka chosen
    Hakutaka is a high-speed train service operating on Japan’s Hokuriku Shinkansen line, connecting Tokyo with cities along the Sea of Japan coast.
  • B. Hōshō
    Hōshō was the Imperial Japanese Navy’s pioneering aircraft carrier and the world’s first purpose-built carrier to enter service.
  • C. Taketoyo
    Taketoyo is a coastal town in central Japan known for its industrial facilities and location within Aichi Prefecture.
  • D. Hiranaka
    Hiranaka is a Japanese surname borne by individuals such as former professional boxer Akinobu Hiranaka.
  • E. Takaishi
    Takaishi is a city in Osaka Prefecture, Japan, known as a small industrial and residential hub within the Osaka metropolitan area.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec25e9a14819081fa06fc601f295d completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffe46175b88190ae687073ddaa3d22 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 1:29 a.m.