Triple
T16328130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 27 |
E396476
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object |
Pier 29
Pier 29 is a waterfront pier, likely part of a numbered pier system in a harbor or port area, used for maritime, commercial, or recreational activities.
|
E1216377
|
NE FINISHED |
How this triple was built (4 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 29 | Statement: [Pier 27, near, Pier 29]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 29 Context triple: [Pier 27, near, Pier 29]
-
A.
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.
-
B.
Pier 25
Pier 25 is a recreational pier in Manhattan’s Hudson River Park featuring a playground, mini-golf, sports courts, and waterfront views.
-
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 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.
-
E.
Pier 54
Pier 54 is a historic waterfront pier and popular tourist stop along Seattle’s Alaskan Way, known for its shops, eateries, and views of Elliott Bay.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Pier 29 Triple: [Pier 27, near, Pier 29]
Generated description
Pier 29 is a waterfront pier, likely part of a numbered pier system in a harbor or port area, used for maritime, commercial, or recreational activities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pier 29 Target entity description: Pier 29 is a waterfront pier, likely part of a numbered pier system in a harbor or port area, used for maritime, commercial, or recreational activities.
-
A.
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.
-
B.
Pier 25
Pier 25 is a recreational pier in Manhattan’s Hudson River Park featuring a playground, mini-golf, sports courts, and waterfront views.
-
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 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.
-
E.
Pier 54
Pier 54 is a historic waterfront pier and popular tourist stop along Seattle’s Alaskan Way, known for its shops, eateries, and views of Elliott Bay.
- F. None of above. chosen
Provenance (5 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dcd034819081d849003d918245 |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00580d372c81908fcc267cdc3812a7 |
completed | May 10, 2026, 10:03 a.m. |
| NEDg | Description generation | batch_6a0059aef1e88190a77ed6036c546718 |
completed | May 10, 2026, 10:10 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a005a2411608190b0fd5dbb68c47fe4 |
completed | May 10, 2026, 10:12 a.m. |
Created at: April 10, 2026, 5:07 a.m.