Triple
T5377774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaskan Way |
E113004
|
entity |
| Predicate | hasPier |
P15921
|
FINISHED |
| Object |
Pier 66
Pier 66 is a major Seattle waterfront complex that serves as a cruise ship terminal, event venue, and public recreation area along Elliott Bay.
|
E524840
|
NE FINISHED |
How this triple was built (4 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: Pier 66 | Statement: [Alaskan Way, hasPier, Pier 66]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 66 Context triple: [Alaskan Way, hasPier, Pier 66]
-
A.
Pier 66
Pier 66 is a Hudson River waterfront pier on Manhattan’s West Side known for its recreational boating, public access, and views of the New York City skyline.
-
B.
Pier 61
Pier 61 is a Hudson River waterfront pier in Manhattan best known today as part of the Chelsea Piers sports and entertainment complex.
-
C.
Pier 64
Pier 64 is a recreational waterfront pier in Manhattan’s Hudson River Park, offering open green space, river views, and public amenities along the Hudson River.
-
D.
Pier 63
Pier 63 is a recreational pier and public space along Manhattan’s Hudson River waterfront, known for its parkland, river views, and cultural and leisure activities.
-
E.
Pier 63
Pier 63 is a waterfront pier and public space located along Seattle’s Alaskan Way on Elliott Bay.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Pier 66 Triple: [Alaskan Way, hasPier, Pier 66]
Generated description
Pier 66 is a major Seattle waterfront complex that serves as a cruise ship terminal, event venue, and public recreation area along Elliott Bay.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pier 66 Target entity description: Pier 66 is a major Seattle waterfront complex that serves as a cruise ship terminal, event venue, and public recreation area along Elliott Bay.
-
A.
Pier 66
Pier 66 is a Hudson River waterfront pier on Manhattan’s West Side known for its recreational boating, public access, and views of the New York City skyline.
-
B.
Pier 61
Pier 61 is a Hudson River waterfront pier in Manhattan best known today as part of the Chelsea Piers sports and entertainment complex.
-
C.
Pier 64
Pier 64 is a recreational waterfront pier in Manhattan’s Hudson River Park, offering open green space, river views, and public amenities along the Hudson River.
-
D.
Pier 63
Pier 63 is a recreational pier and public space along Manhattan’s Hudson River waterfront, known for its parkland, river views, and cultural and leisure activities.
-
E.
Pier 63
Pier 63 is a waterfront pier and public space located along Seattle’s Alaskan Way on Elliott Bay.
- F. None of above. chosen
Provenance (5 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86cb13ac81909dc364e7d3605844 |
completed | March 20, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf7fd0a2c48190ba0c2e3259c3691f |
completed | March 22, 2026, 5:36 a.m. |
| NEDg | Description generation | batch_69bf80e2f34081909bcc695e1b91e3ef |
completed | March 22, 2026, 5:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf813985d881908801f1eee573c220 |
completed | March 22, 2026, 5:42 a.m. |
Created at: March 20, 2026, 2:03 p.m.