Triple

T10088608
Position Surface form Disambiguated ID Type / Status
Subject Link 2 Line E215283 entity
Predicate serves P98 FINISHED
Object Redmond E214491 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: [Link 2 Line, serves, Redmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redmond
Context triple: [Link 2 Line, serves, Redmond]
  • A. Redmond chosen
    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
    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_69ca83a1eed081908b2e9580f2ebeea7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd057e32881908bf630559af94906 completed April 2, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2cbd822a08190841e51862e5e1e27 completed April 5, 2026, 8:53 p.m.
Created at: March 30, 2026, 9:01 p.m.