Triple
T12181741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFTP |
E290235
|
entity |
| Predicate | locatedInMunicipality |
P40
|
FINISHED |
| Object | Pirkkala |
E381146
|
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: Pirkkala | Statement: [EFTP, locatedInMunicipality, Pirkkala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pirkkala Context triple: [EFTP, locatedInMunicipality, Pirkkala]
-
A.
Pirkkala
chosen
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.
-
B.
Janakkala
Janakkala is a municipality in southern Finland known for its rural landscapes and historical churches, located within the Kanta-Häme region.
-
C.
Kuokkala
Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
-
D.
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.
-
E.
Kankaanpää
Kankaanpää is a small town and municipality in the Satakunta region of western Finland, known for its surrounding forests and lakes.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef5a0824819097e41163e3092b68 |
completed | May 9, 2026, 8:24 a.m. |
Created at: April 8, 2026, 9:50 p.m.