Triple

T14764656
Position Surface form Disambiguated ID Type / Status
Subject Seto Ohashi Bridge E346961 entity
Predicate connectsCity P4245 FINISHED
Object Sakaide NE NERFINISHED

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: Sakaide | Statement: [Seto Ohashi Bridge, connectsCity, Sakaide]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sakaide
Context triple: [Seto Ohashi Bridge, connectsCity, Sakaide]
  • A. Sakaide chosen
    Sakaide is a coastal city in Japan known for its industrial port facilities and its location near the Seto Ohashi Bridge in Kagawa Prefecture on Shikoku Island.
  • B. Mikasuki
    Mikasuki is a Native American language of the Muskogean family, traditionally spoken by the Miccosukee and some Seminole people in the southeastern United States.
  • C. Sakae
    Sakae is a major downtown commercial and entertainment district in Nagoya, Japan, known for its shopping, nightlife, and landmark attractions.
  • D. Takatsuki
    Takatsuki is a city in northern Osaka Prefecture, Japan, known as a residential and commercial hub between Osaka and Kyoto.
  • E. Suzuya
    Suzuya is a Japanese Mogami-class heavy cruiser of the Imperial Japanese Navy that served during World War II.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7f3a1608190b1b17624003a0c7f completed April 14, 2026, 11:04 p.m.
Created at: April 10, 2026, 1:30 a.m.