Triple

T20969937
Position Surface form Disambiguated ID Type / Status
Subject Western Washington E516466 entity
Predicate hasMajorCity P316 FINISHED
Object Redmond 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: Redmond | Statement: [Western Washington, hasMajorCity, Redmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redmond
Context triple: [Western Washington, hasMajorCity, Redmond]
  • A. Redmond
    Redmond is a surname of English origin borne by various notable individuals, including figures in entertainment and public life.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. Renton
    Renton is a small town in West Dunbartonshire, Scotland, situated on the River Leven between Dumbarton and Alexandria.
  • 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_69e0b4fee5ac8190875fa9ceba1a5e5e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb9f53e88190847f93e0bbca6ea0 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:43 p.m.