Triple

T21371859
Position Surface form Disambiguated ID Type / Status
Subject Köping E527084 entity
Predicate locatedOnRiver P165 FINISHED
Object Köping 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: Köping River | Statement: [Köping, locatedOnRiver, Köping River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Köping River
Context triple: [Köping, locatedOnRiver, Köping River]
  • A. Tyrma River
    The Tyrma River is a significant watercourse in Russia’s Amur region, known primarily as an important tributary within the Bureya River basin.
  • B. Nyköpingsån river
    Nyköpingsån river is a watercourse in southeastern Sweden that flows through the town of Nyköping before emptying into the Baltic Sea.
  • C. Skellefte River
    The Skellefte River is a major river in northern Sweden that flows through Västerbotten County to the Gulf of Bothnia and has historically supported regional mining, hydropower, and settlement.
  • D. Rönne River
    The Rönne River is a significant watercourse in southern Sweden that flows through the province of Skåne before emptying into the Skälderviken bay of the Kattegat.
  • E. Köpingsån chosen
    Köpingsån is a river in central Sweden that flows through the town of Köping before emptying into Lake Mälaren.
  • 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_69e0b51e80808190ba5cb05667af02a9 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0af44d88190aedd3b2127bb297d completed April 22, 2026, 11:27 a.m.
Created at: April 16, 2026, 5:10 p.m.