Triple

T7034381
Position Surface form Disambiguated ID Type / Status
Subject Region of Kainuu E163343 entity
Predicate contains P35 FINISHED
Object Sotkamo E642469 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: Sotkamo | Statement: [Region of Kainuu, contains, Sotkamo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sotkamo
Context triple: [Region of Kainuu, contains, Sotkamo]
  • A. Sotkamo chosen
    Sotkamo is a municipality in eastern Finland known for its mining industry, outdoor recreation, and the popular Vuokatti ski and sports resort area.
  • B. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • C. Loviisa
    Loviisa is a small coastal town and municipality in southern Finland known for its historic wooden houses, seaside location, and nuclear power plant.
  • D. Ylivieska
    Ylivieska is a small town in Northern Ostrobothnia, Finland, known as a regional commercial and service center along the Kalajoki River.
  • E. Kuokkala
    Kuokkala is a residential district of the city of Jyväskylä in central Finland, known for its lakeside location and distinctive bridge connection to the city center.
  • 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_69c6885d691c81908cf7d31083113886 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e212e28c8190bf38ce9a25d2032e completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7cbc1b76081909094a9b2f215e58d completed March 28, 2026, 12:38 p.m.
Created at: March 27, 2026, 2:36 p.m.