Triple

T11263838
Position Surface form Disambiguated ID Type / Status
Subject State Route 520 E266630 entity
Predicate providesRegionalAccessBetween P24718 FINISHED
Object Bellevue and Redmond E552530 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: Bellevue and Redmond | Statement: [State Route 520, providesRegionalAccessBetween, Bellevue and Redmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bellevue and Redmond
Context triple: [State Route 520, providesRegionalAccessBetween, Bellevue and Redmond]
  • A. Redmond
    Redmond is a growing city in Deschutes County, Oregon, known as a regional hub for transportation, outdoor recreation, and access to Central Oregon’s high desert and Cascade Mountains.
  • B. City of Redmond chosen
    The City of Redmond is a municipal government in Washington State best known as the home of Microsoft and for its vibrant community events and parks.
  • C. Kirkland
    Kirkland is a surname most notably associated with American ballerina Gelsey Kirkland.
  • D. Kirkland
    Kirkland is a suburban town located on the Island of Montreal in the Canadian province of Quebec.
  • E. Lynnwood
    Lynnwood is a suburban city in Snohomish County, Washington, known as a major retail and residential hub just north of Seattle.
  • 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_69d6aac7953c8190b82caf9d7640fdf9 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e94d56048190bf808e1bc2188714 completed April 9, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_69e542ab02708190b40a96edd56a6519 completed April 19, 2026, 9:01 p.m.
Created at: April 8, 2026, 9:31 p.m.