Triple
T17259557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjøvik Region |
E418973
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Lake Mjøsa |
E65750
|
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: Lake Mjøsa | Statement: [Gjøvik Region, near, Lake Mjøsa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lake Mjøsa Context triple: [Gjøvik Region, near, Lake Mjøsa]
-
A.
Mjøsa Lake
chosen
Mjøsa Lake is Norway’s largest lake, located in the southeastern part of the country and known for its scenic surroundings and historic towns along its shores.
-
B.
Storavatnet
Storavatnet is a lake located near the village of Svortland on the island of Bømlo in Vestland county, Norway.
-
C.
Breiddalsvatnet
Breiddalsvatnet is a lake located in Skjåk municipality in Innlandet county, Norway, known for its mountainous surroundings and role in local outdoor recreation.
-
D.
Sørvatnet
Sørvatnet is a lake located near the village of Svortland in Bømlo municipality in Vestland county, Norway.
-
E.
Lake Norsjø
Lake Norsjø is a large inland lake in Telemark, Norway, known as an important link in the Telemark Canal and a popular area for boating and recreation.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6fa940819089046d1b12dede2c |
completed | April 19, 2026, 1:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a017101d5dc8190ac6507344897b0f3 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:39 a.m.