Triple

T19791982
Position Surface form Disambiguated ID Type / Status
Subject Lödöse E475434 entity
Predicate locatedOnRiver P165 FINISHED
Object Göta älv 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: Göta älv | Statement: [Lödöse, locatedOnRiver, Göta älv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Göta älv
Context triple: [Lödöse, locatedOnRiver, Göta älv]
  • A. Göta älv chosen
    Göta älv is a major river in southwestern Sweden that flows from Lake Vänern to the Kattegat, passing through the city of Gothenburg and serving as an important waterway for transport and industry.
  • B. Eskilstunaån
    Eskilstunaån is a river in central Sweden that drains Lake Hjälmaren and flows westward through the city of Eskilstuna toward Lake Mälaren.
  • C. Byälven
    Byälven is a river in western Sweden that flows into Lake Vänern, contributing significantly to its water system.
  • D. Västerdalälven
    Västerdalälven is a major river in central Sweden that forms one of the two main headwaters of the Dalälven, flowing through the Dalarna region.
  • E. Munksjöån
    Munksjöån is a river in Jönköping, Sweden, that drains Lake Munksjön and flows toward Lake Vättern through the city.
  • 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_69d8e51b014081908b263e167370529a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e653c37a3c819080f195d58adaaa7b completed April 20, 2026, 4:26 p.m.
Created at: April 10, 2026, 1:49 p.m.