Triple
T32729369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finland |
E836905
|
entity |
| Predicate | hasSeaLane |
P10083
|
FINISHED |
| Object | shipping routes between Gulf of Finland and Gulf of Bothnia |
—
|
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: shipping routes between Gulf of Finland and Gulf of Bothnia | Statement: [Finland, hasSeaLane, shipping routes between Gulf of Finland and Gulf of Bothnia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaLane Context triple: [Finland, hasSeaLane, shipping routes between Gulf of Finland and Gulf of Bothnia]
-
A.
hasMajorSeaLane
chosen
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced entity.
-
B.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
-
D.
hasSeaEntry
Indicates that an entity has a direct access point or connection to the sea.
-
E.
hasDestinationSea
Indicates that something is directed or travels toward a sea as its endpoint or target location.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 1, 2026, 1:11 a.m.