Triple
T30140799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King County Water Taxi (West Seattle–Downtown Seattle) |
E766121
|
entity |
| Predicate | dock |
P168481
|
FINISHED |
| Object | Seacrest Dock |
—
|
NE NERFINISHED |
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: Seacrest Dock | Statement: [King County Water Taxi (West Seattle–Downtown Seattle), dock, Seacrest Dock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dock Context triple: [King County Water Taxi (West Seattle–Downtown Seattle), dock, Seacrest Dock]
-
A.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
B.
dockIncludes
Indicates that a dock contains, encompasses, or has as part of its structure the specified element or component.
-
C.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
D.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
-
E.
dockable
Indicates that one entity is capable of being securely connected or attached to another, typically in a way that allows them to function together as a unit.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8785f8819090c5162945b8acc6 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:17 p.m.