Triple

T21308828
Position Surface form Disambiguated ID Type / Status
Subject Southern Savonia E525273 entity
Predicate contains P35 FINISHED
Object Enonkoski 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: Enonkoski | Statement: [Southern Savonia, contains, Enonkoski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Enonkoski
Context triple: [Southern Savonia, contains, Enonkoski]
  • A. Enonkoski chosen
    Enonkoski is a small municipality in Eastern Finland known for its lakeside scenery, rural character, and proximity to the Saimaa lake system.
  • B. Onkisalo
    Onkisalo is an island located in Lake Päijänne in Finland.
  • C. Oohenonpa
    Oohenonpa is a band of the Lakota people, historically known as the Two Kettles, who are part of the larger Sioux Nation of the North American Great Plains.
  • D. Peulla
    Peulla is a small, remote village in southern Chile’s Los Lagos Region, known as a scenic gateway for lake crossings through the Andes between Chile and Argentina.
  • E. Pornainen
    Pornainen is a small rural municipality in southern Finland, located within the Greater Helsinki region.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75aa916548190a11f8bb4255e3fed completed April 21, 2026, 11:08 a.m.
Created at: April 16, 2026, 4:06 p.m.