Triple
T2888045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Inlet |
E59552
|
entity |
| Predicate | isNavigationRouteFor |
P14917
|
FINISHED |
| Object | cargo ships serving Anchorage |
—
|
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: cargo ships serving Anchorage | Statement: [Cook Inlet, isNavigationRouteFor, cargo ships serving Anchorage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigationRouteFor Context triple: [Cook Inlet, isNavigationRouteFor, cargo ships serving Anchorage]
-
A.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
B.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
C.
isKeyRoute
Indicates that a route plays a primary or strategically important role within a network or system.
-
D.
isNumberedRouteIn
Indicates that a numbered route (such as a highway or road with an assigned number) is located within or passes through a specified geographic or administrative area.
-
E.
hasNavigationUse
chosen
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe047aa7c8190a0ed570c13f3a1a2 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.