Triple

T9167974
Position Surface form Disambiguated ID Type / Status
Subject Kanta-Häme E220011 entity
Predicate contains P35 FINISHED
Object Riihimäki E691776 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: Riihimäki | Statement: [Kanta-Häme, contains, Riihimäki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riihimäki
Context triple: [Kanta-Häme, contains, Riihimäki]
  • A. Riihimäki chosen
    Riihimäki is a Finnish town known as a regional railway hub and industrial center located north of Helsinki.
  • B. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • C. Kouvola
    Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
  • D. 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.
  • E. Mikkeli
    Mikkeli is a city in eastern Finland known as an important regional center in the Finnish Lakeland area, noted for its lakeside scenery and historical 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaadfb50881909b9127f92e4b3e21 completed April 1, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d74fa545b8819092809c605542476a completed April 9, 2026, 7:05 a.m.
Created at: March 30, 2026, 7:22 p.m.