Triple

T19822913
Position Surface form Disambiguated ID Type / Status
Subject Lake Pyhäjärvi (Tampere) E476243 entity
Predicate borders P224 FINISHED
Object Pirkkala 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: Pirkkala | Statement: [Lake Pyhäjärvi (Tampere), borders, Pirkkala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pirkkala
Context triple: [Lake Pyhäjärvi (Tampere), borders, Pirkkala]
  • A. Pirkkala chosen
    Pirkkala is a municipality in the Pirkanmaa region of southern Finland, located near the city of Tampere and known for its growing residential areas and proximity to Tampere-Pirkkala Airport.
  • B. Janakkala
    Janakkala is a municipality in southern Finland known for its rural landscapes and historical churches, located within the Kanta-Häme region.
  • C. Kuokkala
    Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
  • D. 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.
  • E. Porkkala
    Porkkala is a peninsula in southern Finland that was leased to the Soviet Union as a naval base after World War II and returned to Finnish control in 1956.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6550070c4819099e1f057b9a8849e completed April 20, 2026, 4:32 p.m.
Created at: April 10, 2026, 1:50 p.m.