Triple
T821743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillehammer |
E17762
|
entity |
| Predicate | locatedNear |
P294
|
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: [Lillehammer, locatedNear, Lake Mjøsa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lake Mjøsa Context triple: [Lillehammer, locatedNear, 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.
Norsjø
Norsjø is a large lake in Telemark, Eastern Norway, known as an important part of the Telemark Canal waterway system.
-
C.
Oslofjord
Oslofjord is a large inlet in southeastern Norway known for its islands, coastal towns, and role as the maritime gateway to Oslo.
-
D.
Saltsjön
Saltsjön is a bay of the Baltic Sea forming part of the inner Stockholm archipelago and the main sea approach to central Stockholm.
-
E.
Lake Mälaren
Lake Mälaren is a large freshwater lake in eastern Sweden that connects to the Baltic Sea and has Stockholm situated on its shores.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab7aea38819092a0860ec6e2a033 |
completed | March 1, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac2a0906408190bd54e6308af30631 |
completed | March 7, 2026, 1:37 p.m. |
Created at: March 1, 2026, 7:38 p.m.