Triple
T4292297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chukchi Peninsula |
E99622
|
entity |
| Predicate | seaRouteSignificance |
P10083
|
FINISHED |
| Object | part of Northern Sea Route approaches |
—
|
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: part of Northern Sea Route approaches | Statement: [Chukchi Peninsula, seaRouteSignificance, part of Northern Sea Route approaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaRouteSignificance Context triple: [Chukchi Peninsula, seaRouteSignificance, part of Northern Sea Route approaches]
-
A.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
-
B.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
D.
maritimeGatewayFor
Indicates a relationship where one location serves as the primary seaport or ocean-access point enabling maritime connectivity and trade for another location.
-
E.
hasMajorSeaLane
chosen
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3508035a08190b752c8edce0aff86 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.