Triple
T29104987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anacortes–San Juan Islands ferry routes |
E736737
|
entity |
| Predicate | hubPort |
P423
|
FINISHED |
| Object | Anacortes Ferry Terminal |
—
|
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 Ferry Terminal | Statement: [Anacortes–San Juan Islands ferry routes, hubPort, Anacortes Ferry Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hubPort Context triple: [Anacortes–San Juan Islands ferry routes, hubPort, Anacortes Ferry Terminal]
-
A.
hubFor
chosen
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
B.
hubType
Indicates the specific kind or category of hub associated with an entity or connection.
-
C.
homePortContext
Indicates the relationship in which a specific port serves as the designated home or base port for a vessel or maritime entity within a given context.
-
D.
homePort
Indicates that a vessel or mobile entity is based at, registered to, or primarily operates from a particular port or harbor.
-
E.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
- 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_69f661b93fe48190b846fb7654dc7b7d |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:15 a.m.