Triple
T4843004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piers in Manhattan |
E108220
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Pier 51 |
E312552
|
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: Pier 51 | Statement: [Piers in Manhattan, hasPart, Pier 51]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 51 Context triple: [Piers in Manhattan, hasPart, Pier 51]
-
A.
Pier 51
chosen
Pier 51 is a recreational pier within Manhattan’s Hudson River Park, known for its playground, water features, and riverside views.
-
B.
Pier 5
Pier 5 is a recreational pier in Brooklyn Bridge Park known for its sports fields, waterfront views, and public gathering spaces along the Brooklyn waterfront.
-
C.
Pier 50
Pier 50 is one of the historic waterfront piers along San Francisco’s Embarcadero, used primarily for maritime and industrial purposes.
-
D.
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.
-
E.
Pier 48
Pier 48 is a historic waterfront pier in San Francisco’s Mission Bay area, known for its industrial maritime architecture and redevelopment plans as part of the city’s evolving shoreline.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6cff1b008190b537feea0e0cc88f |
completed | March 20, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be89d3358c8190bb85ec1835a9f095 |
completed | March 21, 2026, 12:06 p.m. |
Created at: March 20, 2026, 1:25 p.m.