Triple

T21073666
Position Surface form Disambiguated ID Type / Status
Subject Pier 55 E519174 entity
Predicate hasNearbyPier P138877 FINISHED
Object Pier 54 NE NERFINISHED

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 54 | Statement: [Pier 55, hasNearbyPier, Pier 54]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pier 54
Context triple: [Pier 55, hasNearbyPier, Pier 54]
  • A. Pier 54 chosen
    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.
  • 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 46
    Pier 46 is a recreational pier along Manhattan’s Hudson River waterfront, featuring open green space, seating, and river views as part of the larger Hudson River Park.
  • E. Pier 45
    Pier 45 is a popular recreational pier in Manhattan’s Greenwich Village, known for its lawns, waterfront views, and role as a gathering spot along the Hudson River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b506e59c8190849b71ed07929215 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e702d491a08190a9f5f28c0b72d38c completed April 21, 2026, 4:53 a.m.
Created at: April 16, 2026, 2:47 p.m.