Triple

T21775281
Position Surface form Disambiguated ID Type / Status
Subject Nes (Viken) E537555 entity
Predicate locatedAlong P2409 FINISHED
Object Glomma River NE NERFINISHED

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 River | Statement: [Nes (Viken), locatedAlong, Glomma River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Glomma River
Context triple: [Nes (Viken), locatedAlong, Glomma River]
  • A. Glomma chosen
    Glomma is Norway’s longest and largest river, flowing through Eastern Norway before emptying into the Oslofjord.
  • B. Glomma valley
    Glomma valley is a river valley in Norway shaped by and named after the country’s longest river, the Glåma (Glomma).
  • C. Drammenselva
    Drammenselva is a major river in southeastern Norway known for its historical timber floating, hydroelectric power production, and salmon fishing.
  • D. Valldalselva river
    Valldalselva river is a Norwegian river known for flowing through the scenic Valldal valley, popular for salmon fishing and outdoor recreation.
  • E. Glåma river
    The Glåma river, also known as Glomma, is Norway’s longest and largest river, flowing through eastern Norway from the Trøndelag region to the Oslofjord.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04627bd488190bbc1fde8db417b55 completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:51 p.m.