Triple
T8660719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 7 |
E205539
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pier 9 |
E207107
|
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 9 | Statement: [Pier 7, near, Pier 9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 9 Context triple: [Pier 7, near, Pier 9]
-
A.
Pier 9
chosen
Pier 9 is a waterfront pier along San Francisco’s Embarcadero known for its scenic bay views and proximity to downtown attractions.
-
B.
Pier 90
Pier 90 is a Manhattan cruise and passenger ship terminal on the Hudson River, historically used for transatlantic liners and now serving modern cruise operations.
-
C.
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.
-
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.
Municipal Pier 9
Municipal Pier 9 is a historic Philadelphia waterfront pier that has been redeveloped into the arts and community space now known as Cherry Street Pier.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48701c748190a5f7bd9e2da0e5e9 |
completed | March 31, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cef37efbf08190805fbb270a4bce37 |
completed | April 2, 2026, 10:53 p.m. |
Created at: March 30, 2026, 6:30 p.m.