Triple
T12792158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrskylä |
E305794
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Pukkila |
E1180063
|
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: Pukkila | Statement: [Myrskylä, sharesBorderWith, Pukkila]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pukkila Context triple: [Myrskylä, sharesBorderWith, Pukkila]
-
A.
Pukkila
chosen
Pukkila is a small rural municipality in southern Finland, located within the Greater Helsinki region.
-
B.
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.
-
C.
Tikkakoski
Tikkakoski is a district in Jyväskylä, Finland, known for its military air base and role as a key center for the Finnish Air Force.
-
D.
Kangasala
Kangasala is a Finnish town and municipality in the Pirkanmaa region, known for its scenic ridge landscapes and lakes.
-
E.
Hankasalmi
Hankasalmi is a rural municipality in Central Finland known for its lakes, forests, and outdoor recreational opportunities.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004568c93c81908450887f72de8466 |
completed | May 10, 2026, 8:44 a.m. |
Created at: April 9, 2026, 5:30 p.m.