Triple
T2906001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma Narrows Bridge |
E62764
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | City of 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: City of Tacoma | Statement: [Tacoma Narrows Bridge, connects, City of Tacoma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Tacoma Context triple: [Tacoma Narrows Bridge, connects, City of Tacoma]
-
A.
Royal City, Washington
Royal City, Washington is a small agricultural town in central Washington State known for its orchards and farming-based economy.
-
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.
Long Beach, Washington
Long Beach, Washington is a small coastal city on the Long Beach Peninsula known for its expansive sandy beach, tourism, and seaside attractions.
-
D.
Bremerton
Bremerton is a waterfront city in Washington State known for its naval shipyard and ferry connection to Seattle across Puget Sound.
-
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 (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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0cee7988190875665145c3cd605 |
completed | March 7, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b334049c5c8190b870e790795cbec4 |
completed | March 12, 2026, 9:45 p.m. |
Created at: March 6, 2026, 10:11 p.m.