Triple
T15394666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanin Nos Cape |
E368141
|
entity |
| Predicate | seaRouteRegion |
P51005
|
FINISHED |
| Object | Northern Sea Route vicinity |
—
|
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: Northern Sea Route vicinity | Statement: [Kanin Nos Cape, seaRouteRegion, Northern Sea Route vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaRouteRegion Context triple: [Kanin Nos Cape, seaRouteRegion, Northern Sea Route vicinity]
-
A.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
-
B.
seaAreaCode
Indicates the specific coded maritime or sea area associated with or relevant to an entity.
-
C.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
D.
routeRegion
chosen
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
E.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.