Triple
T8082445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse D |
E188649
|
entity |
| Predicate | locatedInCity |
P40
|
FINISHED |
| Object | SeaTac |
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: SeaTac | Statement: [Concourse D, locatedInCity, SeaTac]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SeaTac Context triple: [Concourse D, locatedInCity, SeaTac]
-
A.
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.
-
B.
Tukwila
Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
-
C.
Edmonds
Edmonds is an English-origin surname borne by various notable individuals in sports, politics, and the arts.
-
D.
Kirkland
Kirkland is a suburban town located on the Island of Montreal in the Canadian province of Quebec.
-
E.
Edmonds, Washington
Edmonds, Washington is a coastal city in Snohomish County known for its Puget Sound waterfront, ferry terminal, and role as a commuter hub north of Seattle.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415cb4688190920868317e77bbff |
completed | March 31, 2026, 3:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea7d3587881909539a7bea05e328a |
completed | April 2, 2026, 5:30 p.m. |
Created at: March 30, 2026, 5:28 p.m.