Triple

T4670188
Position Surface form Disambiguated ID Type / Status
Subject Gudbrandsdalslågen E102941 entity
Predicate partOf P40 FINISHED
Object Vorma–Glomma watercourse system 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: Vorma–Glomma watercourse system | Statement: [Gudbrandsdalslågen, partOf, Vorma–Glomma watercourse system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vorma–Glomma watercourse system
Context triple: [Gudbrandsdalslågen, partOf, Vorma–Glomma watercourse system]
  • A. Glomma chosen
    Glomma is Norway’s longest and largest river, flowing through Eastern Norway before emptying into the Oslofjord.
  • B. Hallingdalselva
    Hallingdalselva is a major river in eastern Norway known for flowing through the Hallingdal valley and supporting hydropower production, fishing, and outdoor recreation.
  • C. Målselva
    Målselva is a major river in Troms, northern Norway, known for its salmon fishing and scenic valley landscapes.
  • D. Moldeelva
    Moldeelva is a river flowing through the Norwegian town of Molde, contributing to its landscape and local environment.
  • E. Beisfjordelva river
    Beisfjordelva river is a Norwegian river in Nordland county that flows through the Beisfjord area before emptying into the Ofotfjord.
  • 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_69bd43d9cba4819086c1ab1c2d9d2133 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd634ef5608190925663e988e3585b completed March 20, 2026, 3:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69be104a596c8190903c208c892da186 completed March 21, 2026, 3:28 a.m.
Created at: March 20, 2026, 1:15 p.m.