Triple

T8660718
Position Surface form Disambiguated ID Type / Status
Subject Pier 7 E205539 entity
Predicate near P350 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: [Pier 7, near, Pier 5]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Pier 5
Context triple: [Pier 7, near, 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 57
    Pier 57 is a historic, repurposed pier on Manhattan’s west side that now serves as a mixed-use cultural, retail, and public space overlooking the Hudson River.
  • D. 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.
  • E. Pier 51
    Pier 51 is a recreational pier within Manhattan’s Hudson River Park, known for its playground, water features, and riverside views.
  • 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_69ceccfda1dc8190a3b93b1c7e813f33 completed April 2, 2026, 8:09 p.m.
Created at: March 30, 2026, 6:30 p.m.