Triple
T30141534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colman Dock (Pier 52) |
E766140
|
entity |
| Predicate | servesRouteAcross |
P196821
|
FINISHED |
| Object | Puget Sound |
—
|
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: Puget Sound | Statement: [Colman Dock (Pier 52), servesRouteAcross, Puget Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRouteAcross Context triple: [Colman Dock (Pier 52), servesRouteAcross, Puget Sound]
-
A.
servesRoute
Indicates that a service, vehicle, or provider operates along or provides transportation for a specified route.
-
B.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
C.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
D.
serviceRoute
Indicates that a service (such as a transport or delivery operation) follows or is assigned to a particular route.
-
E.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
- 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_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: April 29, 2026, 7:17 p.m.