Triple
T21146394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 56 |
E521066
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pier 57 |
—
|
NE NERFINISHED |
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: Pier 57 | Statement: [Pier 56, near, Pier 57]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 57 Context triple: [Pier 56, near, Pier 57]
-
A.
Pier 57
Pier 57 is a historic waterfront pier and entertainment complex on Seattle’s Elliott Bay, featuring restaurants, shops, and attractions along the city’s central waterfront.
-
B.
Pier 57
chosen
Pier 57 is a historic, repurposed pier on Manhattan’s west side that now serves as a mixed-use cultural, retail, and public space overlooking the Hudson River.
-
C.
Pier 54
Pier 54 is a historic waterfront pier and popular tourist stop along Seattle’s Alaskan Way, known for its shops, eateries, and views of Elliott Bay.
-
D.
Pier 52
Pier 52 is a major ferry terminal on Seattle’s waterfront, serving as a key hub for Washington State Ferries across Puget Sound.
-
E.
Pier 56
Pier 56 is a historic waterfront pier and popular tourist stop along Seattle’s Elliott Bay, featuring restaurants, shops, and scenic views.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fdc25481909d6648e09b069c41 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 2:58 p.m.