Triple

T11038351
Position Surface form Disambiguated ID Type / Status
Subject Colman Dock E260943 entity
Predicate formerName P65 FINISHED
Object Pier 52 E767173 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 52 | Statement: [Colman Dock, formerName, Pier 52]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pier 52
Context triple: [Colman Dock, formerName, Pier 52]
  • A. Pier 52 chosen
    Pier 52 is a major ferry terminal on Seattle’s waterfront, serving as a key hub for Washington State Ferries across Puget Sound.
  • 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 50
    Pier 50 is one of the historic waterfront piers along San Francisco’s Embarcadero, used primarily for maritime and industrial purposes.
  • E. Pier 50
    Pier 50 is a passenger-only ferry terminal on Seattle’s central waterfront, serving as a key hub for King County Water Taxi and other regional ferry services.
  • 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_69d6aa979bdc8190bf0e79104cc098c1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797fe93b081909d58bfd4b42715f0 completed April 9, 2026, 12:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3a9c669608190af97c461beaf9f31 completed April 18, 2026, 3:56 p.m.
Created at: April 8, 2026, 9:26 p.m.