Triple

T4741850
Position Surface form Disambiguated ID Type / Status
Subject Drammen E105261 entity
Predicate locatedOnRiver P165 FINISHED
Object Drammenselva E98765 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: Drammenselva | Statement: [Drammen, locatedOnRiver, Drammenselva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drammenselva
Context triple: [Drammen, 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. Glomma
    Glomma is Norway’s longest and largest river, flowing through Eastern Norway before emptying into the Oslofjord.
  • C. 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.
  • D. Børselva
    Børselva is a river in northern Norway known for flowing into Porsangerfjorden and for its scenic Arctic landscape and salmon fishing.
  • E. Hallingdalselva
    Hallingdalselva is a major river in eastern Norway known for flowing through the Hallingdal valley and supporting hydropower production, fishing, and outdoor recreation.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a7153881909eac451fc7566d25 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a28ca648190a44d178826926812 completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:19 p.m.