Triple
T21129159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemijärvi |
E520636
|
entity |
| Predicate | nearbySkiResort |
P1981
|
FINISHED |
| Object | Pyhä |
—
|
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: Pyhä | Statement: [Kemijärvi, nearbySkiResort, Pyhä]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyhä Context triple: [Kemijärvi, nearbySkiResort, Pyhä]
-
A.
Pyhäntä
Pyhäntä is a small rural municipality in northern Finland known for its forests, lakes, and sparsely populated countryside.
-
B.
Pyhäranta
Pyhäranta is a small coastal municipality in western Finland known for its rural landscapes and proximity to the Baltic Sea.
-
C.
Pyhä-Luosto fells
chosen
Pyhä-Luosto fells are an ancient chain of rounded, forested hills in Finnish Lapland known for their scenic landscapes, outdoor recreation, and geological significance.
-
D.
Haapamäki
Haapamäki is a village in Keuruu, Finland, known as a historic railway junction and hub in the Finnish rail network.
-
E.
Hyrylä
Hyrylä is the main built-up area and administrative center of the municipality of Tuusula in southern Finland.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7223b4c4c8190b9fffa610588651e |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 2:56 p.m.