Triple

T12542314
Position Surface form Disambiguated ID Type / Status
Subject KING E299871 entity
Predicate broadcastArea P2441 FINISHED
Object Seattle–Tacoma E63107 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: Seattle–Tacoma | Statement: [KING, broadcastArea, Seattle–Tacoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seattle–Tacoma
Context triple: [KING, broadcastArea, Seattle–Tacoma]
  • A. Seattle–Bremerton
    Seattle–Bremerton is a major Washington State ferry route across Puget Sound that connects the city of Seattle with the city of Bremerton on the Kitsap Peninsula.
  • B. Tukwila
    Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
  • C. Tacoma, Washington
    Tacoma, Washington is a mid-sized port city in the Pacific Northwest known for its waterfront, industrial history, and vibrant arts and museum scene.
  • D. Tacoma
    Tacoma is a small suburb on the Central Coast of New South Wales, Australia, situated along the Wyong River near Tuggerah Lake.
  • E. SeaTac chosen
    SeaTac is a city in Washington State located between Seattle and Tacoma, best known for housing Seattle–Tacoma International Airport and being served by regional light rail.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9547d6df4819080db8415d386ed38 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c6c21348190b851fce31df307e2 completed May 2, 2026, 10:36 p.m.
Created at: April 8, 2026, 9:57 p.m.