Triple
T29105321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle–Bainbridge Island route |
E736745
|
entity |
| Predicate | isMaritimeRoute |
P166332
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Seattle–Bainbridge Island route, isMaritimeRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaritimeRoute Context triple: [Seattle–Bainbridge Island route, isMaritimeRoute, true]
-
A.
marineRouteType
Indicates the specific kind or classification of a maritime route used for travel, transport, or navigation between locations.
-
B.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
D.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
isMajorMarinePassage
Indicates that a waterway serves as a primary route for significant marine or ocean-going vessel traffic.
- 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_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. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:15 a.m.