Triple

T7438154
Position Surface form Disambiguated ID Type / Status
Subject Washington State Route 99 E171672 entity
Predicate runsThrough P416 FINISHED
Object Edmonds E503134 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: Edmonds | Statement: [Washington State Route 99, runsThrough, Edmonds]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edmonds
Context triple: [Washington State Route 99, runsThrough, Edmonds]
  • A. Edmonds
    Edmonds is an English-origin surname borne by various notable individuals in sports, politics, and the arts.
  • B. Edmonds, Washington chosen
    Edmonds, Washington is a coastal city in Snohomish County known for its Puget Sound waterfront, ferry terminal, and role as a commuter hub north of Seattle.
  • C. Edmonds–Kingston
    Edmonds–Kingston is a major Washington State ferry route across Puget Sound that connects the city of Edmonds on the mainland with the town of Kingston on the Kitsap Peninsula.
  • 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_69c68a64228c8190affaec2a8127ce7b completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f34aa3388190ac300cf934042d78 completed March 27, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83c54c5ec8190bc2adf5a19fdea1c completed March 28, 2026, 8:38 p.m.
Created at: March 27, 2026, 3:13 p.m.