Triple
T16586996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embarcadero, San Francisco |
E402984
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Pier 33 |
E93982
|
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 33 | Statement: [Embarcadero, San Francisco, hasLandmark, Pier 33]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 33 Context triple: [Embarcadero, San Francisco, hasLandmark, Pier 33]
-
A.
Pier 33
chosen
Pier 33 is a waterfront terminal in San Francisco that serves as the primary departure point for ferry trips to Alcatraz Island.
-
B.
Pier 34
Pier 34 is a waterfront pier in Lower Manhattan, New York City, known for its location along the Hudson River near other downtown piers.
-
C.
Pier 23
Pier 23 is a historic waterfront spot along San Francisco’s Embarcadero known for its casual seafood restaurant, bar, and scenic bay views.
-
D.
Pier 35
Pier 35 is a waterfront pier and public space on Manhattan’s East River, known for its recreational areas and views of the New York City skyline.
-
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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599daa508190a9ed6f64138c0e53 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c29465188190a2ba6e3a7b695de3 |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:16 a.m.