Triple
T38475969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation in Kitsap County, Washington |
E915549
|
entity |
| Predicate | footFerryRoute |
P86695
|
FINISHED |
| Object | Bremerton–Port Orchard foot ferry |
—
|
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: Bremerton–Port Orchard foot ferry | Statement: [Transportation in Kitsap County, Washington, footFerryRoute, Bremerton–Port Orchard foot ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footFerryRoute Context triple: [Transportation in Kitsap County, Washington, footFerryRoute, Bremerton–Port Orchard foot ferry]
-
A.
ferryRouteName
chosen
Indicates the specific name assigned to a ferry route that connects two or more locations.
-
B.
hasNearbyFerryRoute
Indicates that there is a ferry route located close to the referenced entity.
-
C.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
D.
bodyOfWaterCrossedByFerry
Indicates that a body of water is traversed or crossed by a ferry service.
-
E.
travelTimeByFerry
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.