Triple

T11854290
Position Surface form Disambiguated ID Type / Status
Subject Torne River E281993 entity
Predicate alsoKnownAs P39 FINISHED
Object Tornionjoki E176811 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: Tornionjoki | Statement: [Torne River, alsoKnownAs, Tornionjoki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tornionjoki
Context triple: [Torne River, alsoKnownAs, Tornionjoki]
  • A. Tornionjoki chosen
    Tornionjoki is a river forming part of the border between Sweden and Finland, known for its salmon fishing and its course into the northern Gulf of Bothnia.
  • B. Ilmajoki
    Ilmajoki is a rural municipality in Southern Ostrobothnia, western Finland, known for its agricultural landscape and strong local cultural traditions.
  • C. Kemijoki
    Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
  • D. Porvoonjoki
    Porvoonjoki is a river in southern Finland that flows through the historic town of Porvoo before emptying into the Gulf of Finland.
  • E. Tourujoki
    Tourujoki is a small river in central Finland that flows through the city of Jyväskylä and into Lake Päijänne.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a697f4108190af984932d2118472 completed April 10, 2026, 7:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4716d92c881908d45cb7b3babb1f7 completed May 1, 2026, 9:25 a.m.
Created at: April 8, 2026, 9:43 p.m.