Triple
T20536722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 86 |
E504217
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pier 90 |
—
|
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 90 | Statement: [Pier 86, near, Pier 90]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 90 Context triple: [Pier 86, near, Pier 90]
-
A.
Pier 90
chosen
Pier 90 is a Manhattan cruise and passenger ship terminal on the Hudson River, historically used for transatlantic liners and now serving modern cruise operations.
-
B.
Pier 97
Pier 97 is a redeveloped waterfront pier on Manhattan’s West Side that serves as a public recreational and event space along the Hudson River.
-
C.
Pier 92
Pier 92 is a former Manhattan waterfront pier on the Hudson River, historically used for shipping and later repurposed for events and exhibitions.
-
D.
Pier 96
Pier 96 is a recreational pier along Manhattan’s Hudson River waterfront, known for activities like kayaking and waterfront access within Hudson River Park.
-
E.
Pier 96
Pier 96 is a San Francisco waterfront pier in the Bayview–Hunters Point area, situated along the city’s industrial shoreline near restored wetlands and open-space areas.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a28f2f1081908f656d790ff182ff |
completed | April 20, 2026, 10:02 p.m. |
Created at: April 16, 2026, 11:37 a.m.