Triple
T31230977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 66 (Seattle) |
E796277
|
entity |
| Predicate | openedAsCruiseTerminalIn |
P185653
|
FINISHED |
| Object | 2000s |
—
|
LITERAL 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: 2000s | Statement: [Pier 66 (Seattle), openedAsCruiseTerminalIn, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsCruiseTerminalIn Context triple: [Pier 66 (Seattle), openedAsCruiseTerminalIn, 2000s]
-
A.
openedAsTerminus
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
B.
newPassengerTerminalOpened
Indicates that a new passenger terminal has begun operations and is now open for use.
-
C.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
D.
openedForShuttleService
Indicates that a location or facility has begun operating to provide shuttle transportation services.
-
E.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
- F. None of above. chosen
Provenance (4 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 29, 2026, 9:10 p.m.