Triple
T9711036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuortane |
E235022
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Lapua |
E791160
|
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: Lapua | Statement: [Kuortane, hasNeighbour, Lapua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lapua Context triple: [Kuortane, hasNeighbour, Lapua]
-
A.
Lapua
chosen
Lapua is a small town in western Finland known for its historical significance, including a former state cartridge factory and its role in the Lapua Movement.
-
B.
Tammela
Tammela is a rural municipality in southern Finland known for its forests, lakes, and national parks such as Torronsuo and Liesjärvi.
-
C.
Laakso
Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
-
D.
Pirkkala
Pirkkala is a municipality in the Pirkanmaa region of southern Finland, located near the city of Tampere and known for its growing residential areas and proximity to Tampere-Pirkkala Airport.
-
E.
Vihti
Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0591208190aa57cc9e2aebafb7 |
completed | April 1, 2026, 10:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f8876748190b0b5efb12031f532 |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:19 p.m.