Triple

T8061510
Position Surface form Disambiguated ID Type / Status
Subject Wako E188130 entity
Predicate hasHighway P385 FINISHED
Object National Route 254 E181898 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: National Route 254 | Statement: [Wako, hasHighway, National Route 254]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: National Route 254
Context triple: [Wako, hasHighway, National Route 254]
  • A. National Route 254 chosen
    National Route 254 is a major Japanese national highway connecting parts of the Tokyo metropolitan area with central Honshu regions.
  • B. National Route 25
    National Route 25 is a major Argentine highway that runs east–west across Chubut Province, linking the Patagonian coast with the Andean region.
  • C. National Route 255
    National Route 255 is a numbered highway in Japan that forms part of the country's national road network.
  • D. National Route 253
    National Route 253 is a designated national highway in Japan that forms part of the country’s numbered trunk road network.
  • E. National Route 250
    National Route 250 is a Japanese national highway that runs along the Seto Inland Sea coast in Hyōgo Prefecture, connecting cities such as Akō and Himeji.
  • 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_69ca82b2f68881908c50560697e210da completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3fcc61c0819085edc26e75c5f6d5 completed March 31, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc93d44c3481908b6e95ce8c78c602 completed April 1, 2026, 3:41 a.m.
Created at: March 30, 2026, 5:26 p.m.