Triple
T11539242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver–Seattle corridor |
E273626
|
entity |
| Predicate | hasUrbanCenter |
P2106
|
FINISHED |
| Object | Everett |
E136257
|
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: Everett | Statement: [Vancouver–Seattle corridor, hasUrbanCenter, Everett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Everett Context triple: [Vancouver–Seattle corridor, hasUrbanCenter, Everett]
-
A.
Everett
Everett is a surname of English origin borne by various notable individuals, including American politician and orator Edward Everett.
-
B.
Everett
Everett is a city in Middlesex County, Massachusetts, located just north of Boston and known for its industrial history and urban residential character.
-
C.
Everett
chosen
Everett is a city in western Washington State, known as a major industrial and maritime hub north of Seattle and home to a large Boeing aircraft assembly plant.
-
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.
Bremerton
Bremerton is a waterfront city in Washington State known for its naval shipyard and ferry connection to Seattle across 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e685ab77908190ac5d59cf2b8c96bf |
completed | April 20, 2026, 7:59 p.m. |
Created at: April 8, 2026, 9:37 p.m.