Triple

T18113829
Position Surface form Disambiguated ID Type / Status
Subject Mjøndalen E433548 entity
Predicate locatedOnRiver P165 FINISHED
Object Drammenselva 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: Drammenselva | Statement: [Mjøndalen, locatedOnRiver, Drammenselva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drammenselva
Context triple: [Mjøndalen, locatedOnRiver, Drammenselva]
  • A. Drammenselva chosen
    Drammenselva is a major river in southeastern Norway known for its historical timber floating, hydroelectric power production, and salmon fishing.
  • B. Akerselva river
    Akerselva river is a historically significant river in Oslo, Norway, known for its former industrial sites, scenic walking paths, and role as a natural boundary between city districts.
  • C. Saltdalselva
    Saltdalselva is a river in Nordland county, Norway, known for flowing through the Saltdal valley and offering notable salmon fishing and scenic natural landscapes.
  • D. Glomma
    Glomma is Norway’s longest and largest river, flowing through Eastern Norway before emptying into the Oslofjord.
  • E. Lysakerelva
    Lysakerelva is a river in the Oslo area of Norway that forms part of the boundary between the municipalities of Oslo and Bærum and is known for its waterfalls, hiking paths, and historical industrial sites.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd3fd9c81909bfe95927f7553e3 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:28 a.m.