Triple
T12190633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otaniemi |
E290450
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Leppävaara |
E398685
|
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: Leppävaara | Statement: [Otaniemi, adjacentTo, Leppävaara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leppävaara Context triple: [Otaniemi, adjacentTo, Leppävaara]
-
A.
Leppävaara
chosen
Leppävaara is a major urban district and transport hub in Espoo, Finland, known for its large shopping center Sello and extensive rail and bus connections.
-
B.
Kankaanpää
Kankaanpää is a small town and municipality in the Satakunta region of western Finland, known for its surrounding forests and lakes.
-
C.
Järvenpää
Järvenpää is a small city in southern Finland known for its lakeside setting and cultural heritage, including its association with composer Jean Sibelius.
-
D.
Lempäälä
Lempäälä is a municipality in the Pirkanmaa region of southern Finland, known for its lakeside landscapes and proximity to the city of Tampere.
-
E.
Rantasalmi
Rantasalmi is a rural municipality in the Southern Savonia region of eastern Finland, known for its lakeside landscapes and traditional Finnish countryside.
- 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_69d91c5340248190b79379423f3a3ca1 |
completed | April 10, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a5a733c819090a6710ab990c38d |
completed | May 9, 2026, 11:28 a.m. |
Created at: April 8, 2026, 9:50 p.m.