Triple
T30141536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colman Dock (Pier 52) |
E766140
|
entity |
| Predicate | isPrimaryFerryTerminalFor |
P160306
|
FINISHED |
| Object | Seattle |
—
|
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: Seattle | Statement: [Colman Dock (Pier 52), isPrimaryFerryTerminalFor, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryFerryTerminalFor Context triple: [Colman Dock (Pier 52), isPrimaryFerryTerminalFor, Seattle]
-
A.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
-
B.
eraOfMajorUseAsFerryTerminal
Indicates the time period during which a location was primarily used as a ferry terminal.
-
C.
ferryTerminalName
Indicates the name assigned to a ferry terminal involved in the relationship or action.
-
D.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
E.
isMainPassengerTerminal
chosen
Indicates that a given passenger terminal serves as the primary or principal terminal within a transportation facility or system.
- F. None of above.
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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:17 p.m.