Triple

T1845927
Position Surface form Disambiguated ID Type / Status
Subject Ostrobothnia E41282 entity
Predicate hasMunicipality P847 FINISHED
Object Kokkola E280624 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: Kokkola | Statement: [Ostrobothnia, hasMunicipality, Kokkola]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kokkola
Context triple: [Ostrobothnia, hasMunicipality, Kokkola]
  • A. Kokkola chosen
    Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
  • B. Lappeenranta
    Lappeenranta is a city in southeastern Finland near the Russian border, known for its lakeside location on Saimaa and its role as a regional commercial and educational center.
  • C. Pori
    Pori is a coastal city in western Finland known for its industrial heritage, port, and annual Pori Jazz Festival.
  • D. Lahti
    Lahti is a city in southern Finland known for its winter sports facilities, particularly ski jumping and cross-country skiing, and for hosting numerous international sporting events.
  • E. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • 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_69a88648cd44819093303206d96d76ad completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb051640c819088a8b28a03f57331 completed March 7, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69afc01252ec8190a14ff51151d8e69e completed March 10, 2026, 6:54 a.m.
Created at: March 4, 2026, 7:33 p.m.