Triple
T10359934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 5 |
E244105
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pier 4 |
E241853
|
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 4 | Statement: [Pier 5, near, Pier 4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 4 Context triple: [Pier 5, near, Pier 4]
-
A.
Pier 4
chosen
Pier 4 is a waterfront pier and recreational area within Brooklyn Bridge Park in Brooklyn, New York City.
-
B.
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.
-
C.
Pier 40
Pier 40 is a large multi-use pier complex on Manhattan’s west side known for its athletic fields, parking facilities, and role as a key recreational hub within Hudson River Park.
-
D.
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.
-
E.
Pier 3
Pier 3 is a historic waterfront pier along San Francisco’s Embarcadero, known for its maritime heritage and scenic views of the bay.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9609c4481908b7d72ecf1adaa73 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d750b6ef248190bdbe16bbb8efcf88 |
completed | April 9, 2026, 7:09 a.m. |
Created at: April 6, 2026, 11:59 a.m.