Triple
T17162363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 48 |
E416511
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Mission Creek Channel |
E636882
|
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: Mission Creek Channel | Statement: [Pier 48, near, Mission Creek Channel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mission Creek Channel Context triple: [Pier 48, near, Mission Creek Channel]
-
A.
Mission Creek
chosen
Mission Creek is a historic waterway and former tidal inlet in San Francisco that once extended inland through what is now the Mission Bay and China Basin area.
-
B.
McKay Creek
McKay Creek is a stream in northeastern Oregon that serves as a local waterway and tributary within Umatilla County’s river system.
-
C.
Anderson Creek
Anderson Creek is a stream in Washington State that serves as one of the natural tributaries feeding into Lake Whatcom.
-
D.
Camas Creek
Camas Creek is a stream in south-central Idaho that flows through the Camas Prairie and feeds into the Big Wood River.
-
E.
Blaine Creek
Blaine Creek is a smaller waterway in Oregon that feeds into the Nestucca River, contributing to the river’s flow and local watershed.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91316108190b0d856d6fa5cd509 |
completed | April 18, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01483969a48190a90268c9560b8cd7 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:37 a.m.