Triple
T29105006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anacortes–San Juan Islands ferry routes |
E736737
|
entity |
| Predicate | hasRoutePattern |
P8151
|
FINISHED |
| Object | Anacortes–Lopez–Shaw–Orcas–Friday Harbor |
—
|
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: Anacortes–Lopez–Shaw–Orcas–Friday Harbor | Statement: [Anacortes–San Juan Islands ferry routes, hasRoutePattern, Anacortes–Lopez–Shaw–Orcas–Friday Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoutePattern Context triple: [Anacortes–San Juan Islands ferry routes, hasRoutePattern, Anacortes–Lopez–Shaw–Orcas–Friday Harbor]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
C.
hasRouteName
Indicates that a route, path, or connection is associated with a specific name or label.
-
D.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
E.
hasCommonRoute
Indicates that two or more entities share at least one overlapping or identical route or path.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 11:15 a.m.