Triple
T21275629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikkeli |
E524379
|
entity |
| Predicate | hasRailwayConnectionTo |
P3791
|
FINISHED |
| Object | Pieksämäki |
—
|
NE NERFINISHED |
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: Pieksämäki | Statement: [Mikkeli, hasRailwayConnectionTo, Pieksämäki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pieksämäki Context triple: [Mikkeli, hasRailwayConnectionTo, Pieksämäki]
-
A.
Pieksämäki
chosen
Pieksämäki is a town in Southern Savonia, Finland, known as a regional transport hub with significant railway and road connections.
-
B.
Kokemäki
Kokemäki is a small town and municipality in the Satakunta region of western Finland, known for its location along the Kokemäenjoki River and its historical roots dating back to medieval times.
-
C.
Pukkila
Pukkila is a small rural municipality in southern Finland, located within the Greater Helsinki region.
-
D.
Luumäki
Luumäki is a rural municipality in South Karelia, southeastern Finland, known for its forests, lakes, and historical significance.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736577fd48190a0038a6ac5678668 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:02 p.m.