Triple
T2315623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embarcadero waterfront |
E51055
|
entity |
| Predicate | contains |
P35
|
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 waterfront, contains, Pier 33]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pier 33 Context triple: [Embarcadero waterfront, contains, 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 3
Pier 3 is a recreational pier within Brooklyn Bridge Park in Brooklyn, New York, featuring open green space, waterfront views, and leisure amenities.
-
C.
Pier 3
Pier 3 is a historic waterfront pier along San Francisco’s Embarcadero, known for its maritime heritage and scenic views of the bay.
-
D.
Pier 39
Pier 39 is a popular waterfront shopping, dining, and entertainment complex in San Francisco best known for its sea lions, bay views, and tourist attractions.
-
E.
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.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc61e72508190b335cda2c7fef130 |
completed | March 7, 2026, 6:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af1f78cce88190a74f9ab6a540fe83 |
completed | March 9, 2026, 7:28 p.m. |
Created at: March 4, 2026, 7:49 p.m.