Triple
T14379543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solør |
E356564
|
entity |
| Predicate | hasMainRiver |
P165
|
FINISHED |
| Object | Glomma |
E96298
|
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: Glomma | Statement: [Solør, hasMainRiver, Glomma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Glomma Context triple: [Solør, hasMainRiver, Glomma]
-
A.
Glomma
chosen
Glomma is Norway’s longest and largest river, flowing through Eastern Norway before emptying into the Oslofjord.
-
B.
Drammenselva
Drammenselva is a major river in southeastern Norway known for its historical timber floating, hydroelectric power production, and salmon fishing.
-
C.
Stjørdalselva
Stjørdalselva is a river in Trøndelag county, Norway, known for flowing through the Stjørdal valley and being a popular destination for salmon fishing.
-
D.
Moldeelva
Moldeelva is a river flowing through the Norwegian town of Molde, contributing to its landscape and local environment.
-
E.
Solbergelva
Solbergelva is a village in Viken county, Norway, situated along the Drammenselva river and functioning largely as a residential suburb of Drammen.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c590660819090652e75418f2747 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:16 a.m.