Triple

T10428209
Position Surface form Disambiguated ID Type / Status
Subject Nedre Eiker E245840 entity
Predicate containsSettlement P847 FINISHED
Object Krokstadelva E440446 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: Krokstadelva | Statement: [Nedre Eiker, containsSettlement, Krokstadelva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krokstadelva
Context triple: [Nedre Eiker, containsSettlement, Krokstadelva]
  • A. Krokstadelva chosen
    Krokstadelva is a town in Viken county, Norway, situated along the Drammenselva river and known historically for its industrial and residential character.
  • B. Verdalselva
    Verdalselva is a river in Trøndelag county, Norway, known for flowing through the Verdalen valley and supporting local agriculture, recreation, and salmon fishing.
  • C. Børselva
    Børselva is a river in northern Norway known for flowing into Porsangerfjorden and for its scenic Arctic landscape and salmon fishing.
  • D. Steinkjerelva
    Steinkjerelva is a river in Trøndelag county, Norway, that flows through the town of Steinkjer before emptying into the inner part of the Trondheimsfjord.
  • E. Moldeelva
    Moldeelva is a river flowing through the Norwegian town of Molde, contributing to its landscape and local environment.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea4a7dcc81909a830e08656a1c0c completed April 7, 2026, 11:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d8dc374f6c8190a44b9da27be343e4 completed April 10, 2026, 11:17 a.m.
Created at: April 6, 2026, 12:13 p.m.