Triple
T3871815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piers 1 through 5 |
E92402
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Pier 5 |
E244105
|
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 5 | Statement: [Piers 1 through 5, hasPart, Pier 5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 5 Context triple: [Piers 1 through 5, hasPart, Pier 5]
-
A.
Pier 5
chosen
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.
-
B.
Pier 57
Pier 57 is a historic waterfront pier and entertainment complex on Seattle’s Elliott Bay, featuring restaurants, shops, and attractions along the city’s central waterfront.
-
C.
Pier 51
Pier 51 is a recreational pier within Manhattan’s Hudson River Park, known for its playground, water features, and riverside views.
-
D.
Pier 4
Pier 4 is a waterfront pier and recreational area within Brooklyn Bridge Park in Brooklyn, New York City.
-
E.
Pier 7
Pier 7 is one of the waterfront recreational piers within Brooklyn Bridge Park in Brooklyn, New York, offering public access and views along the East River.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec5691148190b469af0bee9154db |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b55612ab7081909ab9375da1e4119b |
completed | March 14, 2026, 12:35 p.m. |
Created at: March 9, 2026, 3:20 p.m.