Triple
T12695429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 26 |
E303319
|
entity |
| Predicate | hasNearby |
P350
|
FINISHED |
| Object | Pier 25 |
E301465
|
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 25 | Statement: [Pier 26, hasNearby, Pier 25]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 25 Context triple: [Pier 26, hasNearby, Pier 25]
-
A.
Pier 25
chosen
Pier 25 is a recreational pier in Manhattan’s Hudson River Park featuring a playground, mini-golf, sports courts, and waterfront views.
-
B.
Pier 27
Pier 27 is a waterfront facility in San Francisco that serves as a major cruise ship terminal and gateway for passengers visiting the city.
-
C.
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.
-
D.
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.
-
E.
Pier 52
Pier 52 is a major ferry terminal on Seattle’s waterfront, serving as a key hub for Washington State Ferries across Puget Sound.
- 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_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_69f671ae935c8190a7fc2cf3c0987248 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.