Triple

T10760455
Position Surface form Disambiguated ID Type / Status
Subject Nikko E253811 entity
Predicate hasBridge P386 FINISHED
Object Shinkyo Bridge E884578 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: Shinkyo Bridge | Statement: [Nikko, hasBridge, Shinkyo Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shinkyo Bridge
Context triple: [Nikko, hasBridge, Shinkyo Bridge]
  • A. Shinkyo Bridge chosen
    Shinkyo Bridge is a historic, vermilion-lacquered sacred bridge in Nikkō, Japan, renowned as one of the country’s most beautiful traditional bridges and part of the Nikkō UNESCO World Heritage area.
  • B. Hakucho Bridge
    Hakucho Bridge is a prominent suspension bridge in Muroran, Hokkaido, known for its impressive span and night illumination across Muroran Bay.
  • C. Ebisu Bridge
    Ebisu Bridge is a famous pedestrian bridge in Osaka’s Namba district, known for its neon-lit surroundings and as a popular photo spot overlooking the Dotonbori Canal.
  • D. Tsurumi Bridge
    Tsurumi Bridge is a bridge spanning the Ota River in Japan, serving as a key local transportation link.
  • E. Tsukuda Bridge
    Tsukuda Bridge is a road and pedestrian bridge in Tokyo that spans the Sumida River, connecting the Tsukuda area with central parts of the city.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d731a14c7481909c6f4f9b15dc130f completed April 9, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69de55bb98ec8190914031643c1c7a97 completed April 14, 2026, 2:56 p.m.
Created at: April 8, 2026, 9:16 p.m.