Triple
T7806040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEA |
E180553
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Tacoma |
E21347
|
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: Tacoma | Statement: [SEA, servesCity, Tacoma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tacoma Context triple: [SEA, servesCity, 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.
Tukwila
Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
-
E.
SeaTac
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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf63838b88190a085756db9ca25c4 |
completed | March 30, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5a3bd2e481908e3d3906755b5b7a |
completed | March 31, 2026, 5:23 a.m. |
Created at: March 30, 2026, 4:35 p.m.