Triple
T12158999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Finland |
E289654
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Äänekoski |
E526847
|
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: Äänekoski | Statement: [Central Finland, hasMunicipality, Äänekoski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Äänekoski Context triple: [Central Finland, hasMunicipality, Äänekoski]
-
A.
Äänekoski
chosen
Äänekoski is a Finnish town in Central Finland known for its forest industry, lakeside landscapes, and role as a regional industrial and logistics hub.
-
B.
Kuokkala
Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
-
C.
Kuokkala
Kuokkala is a residential district of the city of Jyväskylä in central Finland, known for its lakeside location and distinctive bridge connection to the city center.
-
D.
Kokkola
Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
-
E.
Lappeenranta
Lappeenranta is a city in southeastern Finland near the Russian border, known for its lakeside location on Saimaa and its role as a regional commercial and educational 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c277e481908351bf4e664dda42 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec869957481909ea4fded01851b70 |
completed | May 9, 2026, 5:38 a.m. |
Created at: April 8, 2026, 9:50 p.m.