Triple
T10073310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirkanmaa |
E213681
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Vesilahti |
E553711
|
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: Vesilahti | Statement: [Pirkanmaa, containsMunicipality, Vesilahti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vesilahti Context triple: [Pirkanmaa, containsMunicipality, Vesilahti]
-
A.
Vesilahti
chosen
Vesilahti is a small rural municipality in the Pirkanmaa region of southwestern Finland, known for its lakeside landscapes and traditional countryside character.
-
B.
Virolahti
Virolahti is a coastal municipality in southeastern Finland, located near the Russian border and known for its maritime nature and birdlife.
-
C.
Vainikkala
Vainikkala is a small Finnish border village and railway station that serves as a key rail crossing point between Finland and Russia on the route between Helsinki and Saint Petersburg.
-
D.
Vanajavesi
Vanajavesi is a prominent lake in southern Finland known for its scenic waterways, cultural heritage, and role in the Kokemäenjoki river basin.
-
E.
Vaajakoski
Vaajakoski is a district of the city of Jyväskylä in Central Finland, known for its lakeside setting and industrial history.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd015ad488190aee3a2bfb58fb855 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e5755a4081909c582bf16dd285e7 |
completed | April 5, 2026, 10:43 p.m. |
Created at: March 30, 2026, 8:59 p.m.