Triple

T14413019
Position Surface form Disambiguated ID Type / Status
Subject Riihimäki E357378 entity
Predicate locatedIn P40 FINISHED
Object Kanta-Häme E220011 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: Kanta-Häme | Statement: [Riihimäki, locatedIn, Kanta-Häme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kanta-Häme
Context triple: [Riihimäki, locatedIn, Kanta-Häme]
  • A. Kanta-Häme chosen
    Kanta-Häme is a region in southern Finland known for its historic towns, lakes, and forests, with Hämeenlinna as its central city.
  • B. Kymenlaakso
    Kymenlaakso is a region in southeastern Finland known for its industrial centers, coastal location along the Gulf of Finland, and historically significant role as a settlement area for evacuees from Karelia.
  • C. Kainuu region
    Kainuu region is an eastern Finnish region known for its vast forests, numerous lakes, and sparsely populated rural landscapes.
  • D. Pirkanmaa region
    Pirkanmaa region is a province in southern Finland centered around the city of Tampere, known for its lakes, industry, and cultural significance.
  • E. Päijät-Häme
    Päijät-Häme is a region in southern Finland known for its lakes, forests, and the city of Lahti as its main urban center.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de90cb3c708190822f5506ebf7ee9d completed April 14, 2026, 7:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d379bc881908b7954c633787165 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 1:17 a.m.