Triple

T12438241
Position Surface form Disambiguated ID Type / Status
Subject Washington State Route 520 E297202 entity
Predicate connects P390 FINISHED
Object 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: Redmond | Statement: [Washington State Route 520, connects, Redmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redmond
Context triple: [Washington State Route 520, connects, 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. Renton
    Renton is a suburban city in Washington State located just southeast of Seattle, known for its Boeing facilities and position at the south end of Lake Washington.
  • D. Renton
    Renton is a small town in West Dunbartonshire, Scotland, situated on the River Leven between Dumbarton and Alexandria.
  • E. Tukwila
    Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
  • 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_69d6ada166c48190b902972cd2408fa3 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d8dc0f881908a3da736d8947ce1 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65ea710d481908371209cb92502a6 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 9:55 p.m.