Triple
T13815435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki region |
E332002
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Hyvinkää |
—
|
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: Hyvinkää | Statement: [Helsinki region, contains, Hyvinkää]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hyvinkää Context triple: [Helsinki region, contains, Hyvinkää]
-
A.
Hyvinkää
chosen
Hyvinkää is a town and municipality in southern Finland known for its railway heritage and location within the Greater Helsinki region.
-
B.
Heinola
Heinola is a small Finnish town in the Päijät-Häme region, known for its lakeside scenery and traditional wooden architecture.
-
C.
Kirkkonummi
Kirkkonummi is a municipality in southern Finland, located just west of Helsinki on the coast of the Gulf of Finland.
-
D.
Järvenpää
Järvenpää is a small city in southern Finland known for its lakeside setting and cultural heritage, including its association with composer Jean Sibelius.
-
E.
Kuokkala
Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
Created at: April 9, 2026, 10:12 p.m.