Triple
T4843020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piers in Manhattan |
E108220
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Pier 16 |
E460008
|
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 16 | Statement: [Piers in Manhattan, hasPart, Pier 16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 16 Context triple: [Piers in Manhattan, hasPart, Pier 16]
-
A.
Pier 16
chosen
Pier 16 is a historic waterfront pier at New York City's South Street Seaport, known for its preserved sailing ships, maritime exhibits, and harbor views.
-
B.
Pier 1
Pier 1 is a waterfront recreational pier in Brooklyn Bridge Park offering green space, views of the Manhattan skyline, and public amenities along the East River.
-
C.
Pier 1
Pier 1 is a historic waterfront pier along San Francisco’s Embarcadero, now used for offices, dining, and public access to the bay.
-
D.
Pier 14
Pier 14 is a public pedestrian pier and popular waterfront viewpoint along San Francisco’s Embarcadero, offering scenic vistas of the bay and city skyline.
-
E.
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.
- 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_69bf186311c88190a8fe34e497e4662b |
completed | March 21, 2026, 10:14 p.m. |
Created at: March 20, 2026, 1:25 p.m.