Triple

T8927181
Position Surface form Disambiguated ID Type / Status
Subject Seattle waterfront piers E212564 entity
Predicate hasPart P35 FINISHED
Object Pier 63 E524710 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 63 | Statement: [Seattle waterfront piers, hasPart, Pier 63]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pier 63
Context triple: [Seattle waterfront piers, hasPart, Pier 63]
  • A. Pier 63
    Pier 63 is a recreational pier and public space along Manhattan’s Hudson River waterfront, known for its parkland, river views, and cultural and leisure activities.
  • B. Pier 63 chosen
    Pier 63 is a waterfront pier and public space located along Seattle’s Alaskan Way on Elliott Bay.
  • C. Pier 62
    Pier 62 is a recreational pier along Manhattan’s west side waterfront that features park space, a carousel, and views of the Hudson River as part of the larger Hudson River Park.
  • D. Pier 62
    Pier 62 is a public waterfront pier and park space on Seattle’s Elliott Bay, known for its views, recreation areas, and community events.
  • E. Pier 60
    Pier 60 is a prominent Hudson River waterfront pier in Manhattan best known for its event spaces, recreational facilities, and role as part of the Chelsea Piers sports and entertainment complex.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6671557c81909f3837ffd6a15ffe completed April 1, 2026, 12:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69d02f88db0881909975af03ed2f3d84 completed April 3, 2026, 9:22 p.m.
Created at: March 30, 2026, 6:57 p.m.