Triple
T5828084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjøvik Line |
E129277
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Gjøvik |
E84018
|
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: Gjøvik | Statement: [Gjøvik Line, namedAfter, Gjøvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjøvik Context triple: [Gjøvik Line, namedAfter, Gjøvik]
-
A.
Gjøvik
chosen
Gjøvik is a town and municipality in Innlandet county, Norway, known for its location along Lake Mjøsa and its mix of industrial heritage and modern sports and cultural facilities.
-
B.
Røyken
Røyken is a former municipality and suburban area in southeastern Norway, located along the Oslofjord and historically part of Buskerud county.
-
C.
Lørenskog
Lørenskog is a suburban municipality in Viken county, Norway, located just east of Oslo and known for its residential areas and commercial centers.
-
D.
Drammen
Drammen is a city and municipality in southeastern Norway known for its riverside setting along the Drammenselva and its role as a regional commercial and transport hub.
-
E.
Lysaker
Lysaker is a key transport and business hub in the western part of the Oslo metropolitan area in Norway, featuring a major railway and commuter center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0341df8dc8190871af068e1f927a2 |
completed | March 22, 2026, 6:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c65fa576888190a3fd0fb3eac72a3f |
completed | March 27, 2026, 10:44 a.m. |
Created at: March 22, 2026, 3:53 p.m.