Triple
T9779625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 2 |
E237332
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pier 1 |
E234434
|
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 1 | Statement: [Pier 2, near, Pier 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 1 Context triple: [Pier 2, near, Pier 1]
-
A.
Pier 1
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Pier 16
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.
-
E.
Pier 51
Pier 51 is a recreational pier within Manhattan’s Hudson River Park, known for its playground, water features, and riverside views.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13663f081909b95563038eb6485 |
completed | April 1, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1bd28b0e48190984cf44d88f324d7 |
completed | April 5, 2026, 1:38 a.m. |
Created at: March 30, 2026, 8:27 p.m.