Triple

T14994037
Position Surface form Disambiguated ID Type / Status
Subject Municipal council of Kirkkonummi E373909 entity
Predicate locatedIn P40 FINISHED
Object Kirkkonummi 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: Kirkkonummi | Statement: [Municipal council of Kirkkonummi, locatedIn, Kirkkonummi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kirkkonummi
Context triple: [Municipal council of Kirkkonummi, locatedIn, Kirkkonummi]
  • A. Kirkkonummi chosen
    Kirkkonummi is a municipality in southern Finland, located just west of Helsinki on the coast of the Gulf of Finland.
  • B. Kuokkala
    Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
  • C. 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.
  • D. Heinola
    Heinola is a small Finnish town in the Päijät-Häme region, known for its lakeside scenery and traditional wooden architecture.
  • E. Kankaanpää
    Kankaanpää is a small town and municipality in the Satakunta region of western Finland, known for its surrounding forests and lakes.
  • 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_69d85ccc84388190aa151e5173370c8d completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded716ebb481908224d2d4f7561b03 completed April 15, 2026, 12:08 a.m.
Created at: April 10, 2026, 2:53 a.m.