Triple
T12695430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 26 |
E303319
|
entity |
| Predicate | hasNearby |
P350
|
FINISHED |
| Object |
Pier 34
Pier 34 is a waterfront pier in Lower Manhattan, New York City, known for its location along the Hudson River near other downtown piers.
|
E999574
|
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 34 | Statement: [Pier 26, hasNearby, Pier 34]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 34 Context triple: [Pier 26, hasNearby, Pier 34]
-
A.
Pier 33
Pier 33 is a waterfront terminal in San Francisco that serves as the primary departure point for ferry trips to Alcatraz Island.
-
B.
Pier 35
Pier 35 is a waterfront pier and public space on Manhattan’s East River, known for its recreational areas and views of the New York City skyline.
-
C.
Pier 84
Pier 84 is a popular recreational pier along Manhattan’s Hudson River waterfront, featuring green space, seating, and riverfront views within Hudson River Park.
-
D.
Pier 84
Pier 84 is a waterfront facility within the Port of Philadelphia used for maritime and cargo-related operations.
-
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. 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 34 Triple: [Pier 26, hasNearby, Pier 34]
Generated description
Pier 34 is a waterfront pier in Lower Manhattan, New York City, known for its location along the Hudson River near other downtown piers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pier 34 Target entity description: Pier 34 is a waterfront pier in Lower Manhattan, New York City, known for its location along the Hudson River near other downtown piers.
-
A.
Pier 33
Pier 33 is a waterfront terminal in San Francisco that serves as the primary departure point for ferry trips to Alcatraz Island.
-
B.
Pier 35
Pier 35 is a waterfront pier and public space on Manhattan’s East River, known for its recreational areas and views of the New York City skyline.
-
C.
Pier 84
Pier 84 is a popular recreational pier along Manhattan’s Hudson River waterfront, featuring green space, seating, and riverfront views within Hudson River Park.
-
D.
Pier 84
Pier 84 is a waterfront facility within the Port of Philadelphia used for maritime and cargo-related operations.
-
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. 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ebd17081909f983567e4b36533 |
completed | April 10, 2026, 8:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c7c4c608190a1786accf8d86141 |
completed | May 2, 2026, 10:36 p.m. |
| NEDg | Description generation | batch_69f67d64ed3481908d434c20796866f9 |
completed | May 2, 2026, 10:40 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f67e82e35081909c4b5fad7e941610 |
completed | May 2, 2026, 10:45 p.m. |
Created at: April 9, 2026, 5:22 p.m.