Triple

T13873368
Position Surface form Disambiguated ID Type / Status
Subject Tervola E333515 entity
Predicate locatedOnRiver P165 FINISHED
Object Kemijoki E122150 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: Kemijoki | Statement: [Tervola, locatedOnRiver, Kemijoki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kemijoki
Context triple: [Tervola, locatedOnRiver, Kemijoki]
  • A. Kemijoki chosen
    Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
  • B. Ilmajoki
    Ilmajoki is a rural municipality in Southern Ostrobothnia, western Finland, known for its agricultural landscape and strong local cultural traditions.
  • C. Kuusjoki
    Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
  • D. Karijoki
    Karijoki is a small rural municipality in western Finland known for its agricultural landscape and quiet countryside.
  • E. Eurajoki
    Eurajoki is a municipality in western Finland, known for hosting the Olkiluoto nuclear power plant on the coast of the Gulf of Bothnia.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0be4031c8190bef5865ec23b18a0 completed April 14, 2026, 9:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c107c20c81909dff0ca4a59fcc55 completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.