Triple
T6187650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sannikov Strait |
E138101
|
entity |
| Predicate | navigationalUse |
P7788
|
FINISHED |
| Object | Arctic shipping route |
—
|
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: Arctic shipping route | Statement: [Sannikov Strait, navigationalUse, Arctic shipping route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalUse Context triple: [Sannikov Strait, navigationalUse, Arctic shipping route]
-
A.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
B.
navigability
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
C.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
D.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
E.
maritimeUsage
chosen
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06217be288190997032c8c4839fa5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.