Triple
T30588711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 53 (Seattle) |
E778589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | building or structure in Seattle |
C28614
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: building or structure in Seattle Context triple: [Pier 53 (Seattle), instanceOf, building or structure in Seattle]
-
A.
skyscraper in Seattle
A skyscraper in Seattle is a tall, multi-story commercial or mixed-use building that defines the city's skyline, often featuring modern architecture, glass facades, and views of Puget Sound and the surrounding mountains.
-
B.
bridge in Seattle
chosen
A bridge in Seattle is a structural crossing—often spanning water or valleys—that connects different parts of the city or region, accommodating vehicles, pedestrians, and sometimes rail while withstanding the Pacific Northwest’s climate and seismic conditions.
-
C.
city in Washington State
A city in Washington State is an incorporated urban municipality within the state’s boundaries that provides local government services, infrastructure, and regulations to its residents and businesses.
-
D.
region of Seattle
A region of Seattle represents a specific geographic area within the city, defined by boundaries and associated with particular neighborhoods, landmarks, and administrative or cultural characteristics.
-
E.
street in Washington State
A street in Washington State is a public roadway within the state's boundaries that facilitates vehicular and pedestrian travel, often connecting residential, commercial, and natural areas under local or state jurisdiction.
- F. None of above.
Provenance (1 batch)
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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:24 p.m.