Triple

T2511454
Position Surface form Disambiguated ID Type / Status
Subject Snohomish County E52708 entity
Predicate containsSettlement P847 FINISHED
Object Edmonds E178135 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: [Snohomish County, containsSettlement, Edmonds]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edmonds
Context triple: [Snohomish County, containsSettlement, Edmonds]
  • A. Edmonds chosen
    Edmonds is an English-origin surname borne by various notable individuals in sports, politics, and the arts.
  • B. 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.
  • C. Kirkland
    Kirkland is a suburban town located on the Island of Montreal in the Canadian province of Quebec.
  • D. Lynnwood
    Lynnwood is a suburban city in Snohomish County, Washington, known as a major retail and residential hub just north of Seattle.
  • E. Federal Way
    Federal Way is a suburban city in Washington State located between Seattle and Tacoma, known for its residential communities, parks, and proximity to Puget Sound.
  • 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_69ab4958e76481908a235377dd921c9e completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd1eeaaac8190a6652861dd42e6b9 completed March 7, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69b48810202c8190a2a8d5ae849b6d9e completed March 13, 2026, 9:56 p.m.
Created at: March 6, 2026, 9:46 p.m.