Triple

T15482929
Position Surface form Disambiguated ID Type / Status
Subject Ylöjärvi E376966 entity
Predicate locatedIn P40 FINISHED
Object Pirkanmaa E213681 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: Pirkanmaa | Statement: [Ylöjärvi, locatedIn, Pirkanmaa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pirkanmaa
Context triple: [Ylöjärvi, locatedIn, Pirkanmaa]
  • A. Pirkanmaa chosen
    Pirkanmaa is a region in southern Finland centered around the city of Tampere, known for its lakes, industry, and cultural significance.
  • B. Vihti
    Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
  • C. Savonia
    Savonia is a historical and cultural region in eastern Finland known for its lakes, forests, and distinct Savonian dialect and traditions.
  • D. Raisio
    Raisio is a town and municipality in southwestern Finland known for its industrial base and as the headquarters of the food company Raisio Group.
  • E. Pirkanmaa region
    Pirkanmaa region is a province in southern Finland centered around the city of Tampere, known for its lakes, industry, and cultural significance.
  • 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f8e6ff08190b130b3a38f4190e7 completed April 16, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2d0f4e648190b9cd9b1464209224 completed May 9, 2026, 12:48 p.m.
Created at: April 10, 2026, 3:40 a.m.