Triple

T8927182
Position Surface form Disambiguated ID Type / Status
Subject Seattle waterfront piers E212564 entity
Predicate hasPart P35 FINISHED
Object Pier 66 E524840 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 66 | Statement: [Seattle waterfront piers, hasPart, Pier 66]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pier 66
Context triple: [Seattle waterfront piers, hasPart, Pier 66]
  • A. Pier 66 chosen
    Pier 66 is a major Seattle waterfront complex that serves as a cruise ship terminal, event venue, and public recreation area along Elliott Bay.
  • B. Pier 66
    Pier 66 is a Hudson River waterfront pier on Manhattan’s West Side known for its recreational boating, public access, and views of the New York City skyline.
  • C. Pier 61
    Pier 61 is a Hudson River waterfront pier in Manhattan best known today as part of the Chelsea Piers sports and entertainment complex.
  • D. Pier 64
    Pier 64 is a recreational waterfront pier in Manhattan’s Hudson River Park, offering open green space, river views, and public amenities along the Hudson River.
  • E. 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.
  • 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_69d047408b20819084d0b9b831f0f2c0 completed April 3, 2026, 11:03 p.m.
Created at: March 30, 2026, 6:57 p.m.