Triple
T33101590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverdale, Washington |
E847063
|
entity |
| Predicate | hasNearbyFerryRouteTo |
P87674
|
FINISHED |
| Object | Seattle, Washington |
—
|
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, Washington | Statement: [Silverdale, Washington, hasNearbyFerryRouteTo, Seattle, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFerryRouteTo Context triple: [Silverdale, Washington, hasNearbyFerryRouteTo, Seattle, Washington]
-
A.
hasNearbyFerryRoute
chosen
Indicates that there is a ferry route located close to the referenced entity.
-
B.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
C.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
D.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
E.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 1, 2026, 1:26 a.m.