Triple
T14501498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gausdal |
E359649
|
entity |
| Predicate | borders |
P224
|
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: [Gausdal, borders, Gjøvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjøvik Context triple: [Gausdal, borders, 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.
Torshov
Torshov is a residential neighborhood in Oslo, Norway, known for its early 20th-century architecture, green spaces, and vibrant local culture.
-
D.
Slemdal
Slemdal is a residential neighborhood in the Vestre Aker borough of Oslo, Norway, known for its green surroundings and affluent character.
-
E.
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.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de94dfe484819086dd971606e6478e |
completed | April 14, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea59f26188190b81af88940a9c95b |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 1:21 a.m.