Triple

T20556612
Position Surface form Disambiguated ID Type / Status
Subject Tacoma Union Station E504735 entity
Predicate city P40 FINISHED
Object Tacoma 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: Tacoma | Statement: [Tacoma Union Station, city, Tacoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tacoma
Context triple: [Tacoma Union Station, city, Tacoma]
  • A. Tacoma
    Tacoma is a small suburb on the Central Coast of New South Wales, Australia, situated along the Wyong River near Tuggerah Lake.
  • B. Tacoma, Washington chosen
    Tacoma, Washington is a mid-sized port city in the Pacific Northwest known for its waterfront, industrial history, and vibrant arts and museum scene.
  • C. Bellingham
    Bellingham is a residential district in southeast London known for its 20th-century housing estates and local community amenities.
  • D. Bellingham
    Bellingham is a small village in Northumberland, England, known as a gateway to the North Tyne valley and the surrounding Northumberland National Park.
  • 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 (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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5de9c008190b8620628fb285e90 completed April 20, 2026, 10:17 p.m.
Created at: April 16, 2026, 11:38 a.m.