Triple
T12969763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirkanmaa |
E321361
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Sastamala |
E128764
|
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: Sastamala | Statement: [Pirkanmaa, hasCity, Sastamala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sastamala Context triple: [Pirkanmaa, hasCity, Sastamala]
-
A.
Sastamala
chosen
Sastamala is a town and municipality in southwestern Finland known for its historical churches, cultural heritage, and scenic lakeside landscapes.
-
B.
Kangasala
Kangasala is a Finnish town and municipality in the Pirkanmaa region, known for its scenic ridge landscapes and lakes.
-
C.
Tammela
Tammela is a rural municipality in southern Finland known for its forests, lakes, and national parks such as Torronsuo and Liesjärvi.
-
D.
Hankasalmi
Hankasalmi is a rural municipality in Central Finland known for its lakes, forests, and outdoor recreational opportunities.
-
E.
Laakso
Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e407e5081909424fc0c22483c28 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73053a1888190a234e8c119a4202a |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 8:34 p.m.