Triple

T4843013
Position Surface form Disambiguated ID Type / Status
Subject Piers in Manhattan E108220 entity
Predicate hasPart P35 FINISHED
Object Pier 84 E321827 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 84 | Statement: [Piers in Manhattan, hasPart, Pier 84]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pier 84
Context triple: [Piers in Manhattan, hasPart, Pier 84]
  • A. Pier 84 chosen
    Pier 84 is a popular recreational pier along Manhattan’s Hudson River waterfront, featuring green space, seating, and riverfront views within Hudson River Park.
  • B. Pier 84
    Pier 84 is a waterfront facility within the Port of Philadelphia used for maritime and cargo-related operations.
  • C. 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.
  • D. Pier 68
    Pier 68 is a public recreational pier and park on Philadelphia’s Delaware River waterfront, known for its fishing spots, river views, and landscaped green space.
  • 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 (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_69bd4409b264819085ab855f3eb5381a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6cff1b008190b537feea0e0cc88f completed March 20, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69bee059e7088190a04124e5918a3c42 completed March 21, 2026, 6:15 p.m.
Created at: March 20, 2026, 1:25 p.m.