Triple

T5905104
Position Surface form Disambiguated ID Type / Status
Subject 皇居 E131323 entity
Predicate 構成要素 P14960 FINISHED
Object 北桔橋門 E76877 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: 北桔橋門 | Statement: [皇居, 構成要素, 北桔橋門]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 北桔橋門
Context triple: [皇居, 構成要素, 北桔橋門]
  • A. 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.
  • B. Ikuchi Bridge
    Ikuchi Bridge is a cable-stayed bridge in Japan that forms part of the scenic Shimanami Kaido route connecting the islands of the Seto Inland Sea.
  • C. Hakucho Bridge
    Hakucho Bridge is a prominent suspension bridge in Muroran, Hokkaido, known for its impressive span and night illumination across Muroran Bay.
  • D. Taipei Bridge
    Taipei Bridge is a major roadway bridge in northern Taiwan that connects Taipei City with New Taipei City across the Tamsui River.
  • E. Nijūbashi Bridge chosen
    Nijūbashi Bridge is a famous pair of arched bridges at the main entrance to Tokyo’s Imperial Palace, known as one of Japan’s most iconic and photographed landmarks.
  • 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_69c0085864a88190a569c05ff7d65f29 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c049fdb3e08190a72337ab4f48bc8e completed March 22, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b16ba6c881908e9a909bf86ea92d completed March 23, 2026, 3:20 a.m.
Created at: March 22, 2026, 3:59 p.m.