Triple
T17257516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mellunmäki station |
E418920
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object |
Mellunmäki
Mellunmäki is a residential district in eastern Helsinki, Finland, known as the terminus area of one of the city’s metro lines.
|
E1259452
|
NE FINISHED |
How this triple was built (4 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: Mellunmäki | Statement: [Mellunmäki station, locatedIn, Mellunmäki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mellunmäki Context triple: [Mellunmäki station, locatedIn, Mellunmäki]
-
A.
Leivonmäki
Leivonmäki is a former rural municipality in Central Finland known for its forests, lakes, and the Leivonmäki National Park.
-
B.
Luumäki
Luumäki is a rural municipality in South Karelia, southeastern Finland, known for its forests, lakes, and historical significance.
-
C.
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.
-
D.
Haapamäki
Haapamäki is a village in Keuruu, Finland, known as a historic railway junction and hub in the Finnish rail network.
-
E.
Pieksämäki
Pieksämäki is a town in Southern Savonia, Finland, known as a regional transport hub with significant railway and road connections.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Mellunmäki Triple: [Mellunmäki station, locatedIn, Mellunmäki]
Generated description
Mellunmäki is a residential district in eastern Helsinki, Finland, known as the terminus area of one of the city’s metro lines.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Mellunmäki Target entity description: Mellunmäki is a residential district in eastern Helsinki, Finland, known as the terminus area of one of the city’s metro lines.
-
A.
Leivonmäki
Leivonmäki is a former rural municipality in Central Finland known for its forests, lakes, and the Leivonmäki National Park.
-
B.
Luumäki
Luumäki is a rural municipality in South Karelia, southeastern Finland, known for its forests, lakes, and historical significance.
-
C.
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.
-
D.
Haapamäki
Haapamäki is a village in Keuruu, Finland, known as a historic railway junction and hub in the Finnish rail network.
-
E.
Pieksämäki
Pieksämäki is a town in Southern Savonia, Finland, known as a regional transport hub with significant railway and road connections.
- F. None of above. chosen
Provenance (5 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6dde4881908e7fc01fd5364616 |
completed | April 19, 2026, 1:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170ff6818819090077dc4a7b774ae |
completed | May 11, 2026, 6:02 a.m. |
| NEDg | Description generation | batch_6a017521c90c819099cea67e4084aa67 |
completed | May 11, 2026, 6:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01760409ac8190ac7714e31e686d9a |
completed | May 11, 2026, 6:24 a.m. |
Created at: April 10, 2026, 5:39 a.m.