Triple
T4842999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piers in Manhattan |
E108220
|
entity |
| Predicate | hasPart |
P35
|
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: [Piers in Manhattan, hasPart, Pier 25]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 25 Context triple: [Piers in Manhattan, hasPart, 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 97
Pier 97 is a redeveloped waterfront pier on Manhattan’s West Side that serves as a public recreational and event space along the Hudson River.
-
E.
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.
- 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_69be5ccdf7a081909624f5cff787e688 |
completed | March 21, 2026, 8:54 a.m. |
Created at: March 20, 2026, 1:25 p.m.