Triple
T16197531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gudvangen |
E393104
|
entity |
| Predicate | connectedToFjordSystem |
P20872
|
FINISHED |
| Object | Sognefjord |
E74083
|
NE 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: Sognefjord | Statement: [Gudvangen, connectedToFjordSystem, Sognefjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToFjordSystem Context triple: [Gudvangen, connectedToFjordSystem, Sognefjord]
-
A.
hasFjord
Indicates that an entity possesses, contains, or is characterized by a fjord as part of its geography or features.
-
B.
hasNearbyFjord
Indicates that one entity is located close to or in the vicinity of a fjord associated with another entity.
-
C.
hydrologicallyConnectedTo
chosen
Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological system.
-
D.
connectsToByLake
Indicates that one entity is linked or joined to another specifically via a lake as the connecting medium or route.
-
E.
isPartOfChainOfLakes
Indicates that a lake belongs to and is one element within a connected sequence of lakes forming a chain.
- F. None of above.
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222dc6b1c8190a3d8a6451ed8b95a |
completed | April 17, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1107344f7c8190bb8d4b75d68cb669 |
completed | May 23, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.