Triple
T5643715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruokolahti |
E124330
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Luumäki |
E238056
|
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: Luumäki | Statement: [Ruokolahti, borders, Luumäki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luumäki Context triple: [Ruokolahti, borders, Luumäki]
-
A.
Luumäki
chosen
Luumäki is a rural municipality in South Karelia, southeastern Finland, known for its forests, lakes, and historical significance.
-
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.
Hyrynsalmi
Hyrynsalmi is a small municipality in the Kainuu region of eastern Finland, known for its forested landscapes, lakes, and outdoor recreation opportunities.
-
D.
Vihti
Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
-
E.
Vaajakoski
Vaajakoski is a district of the city of Jyväskylä in Central Finland, known for its lakeside setting and industrial history.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a1d7af8819092e28ce9fb14d1f1 |
completed | March 22, 2026, 9:07 p.m. |
Created at: March 22, 2026, 3:41 p.m.