Triple

T8701456
Position Surface form Disambiguated ID Type / Status
Subject Hamina E206540 entity
Predicate nearbyCity P350 FINISHED
Object Lappeenranta E21221 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: Lappeenranta | Statement: [Hamina, nearbyCity, Lappeenranta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lappeenranta
Context triple: [Hamina, nearbyCity, Lappeenranta]
  • A. Lappeenranta chosen
    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.
  • B. 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.
  • C. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • D. Lempäälä
    Lempäälä is a municipality in the Pirkanmaa region of southern Finland, known for its lakeside landscapes and proximity to the city of Tampere.
  • E. Kouvola
    Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
  • 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_69ca83555b6c8190abe930dd397e863b completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc58b38cf88190bfdcbac9c340cb96 completed March 31, 2026, 11:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1c3ed827c8190899cb2ae9561765e completed April 5, 2026, 2:07 a.m.
Created at: March 30, 2026, 6:34 p.m.