Triple
T17838338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjeltefjorden |
E445451
|
entity |
| Predicate | formsMaritimeRouteBetween |
P27556
|
FINISHED |
| Object | Bergen and the North Sea |
—
|
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: Bergen and the North Sea | Statement: [Hjeltefjorden, formsMaritimeRouteBetween, Bergen and the North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsMaritimeRouteBetween Context triple: [Hjeltefjorden, formsMaritimeRouteBetween, Bergen and the North Sea]
-
A.
sailingRoute
Indicates a path or course taken by a vessel when traveling by water from one location to another.
-
B.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
C.
hasSeaRouteConnection
chosen
Indicates that there exists a navigable maritime route linking two locations or entities.
-
D.
COASTERRoute
Indicates a route or path specifically designated for a coaster (such as a roller coaster or similar ride) to travel along.
-
E.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d29830c81909fa3ef5a352921b8 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.