Triple
T16415999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leppävaara |
E398685
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Espoo |
E302409
|
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: Espoo | Statement: [Leppävaara, locatedIn, Espoo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Espoo Context triple: [Leppävaara, locatedIn, Espoo]
-
A.
Espoo
chosen
Espoo is Finland’s second-largest city, located just west of Helsinki on the southern coast, known for its technology industry, natural landscapes, and role as part of the Helsinki metropolitan area.
-
B.
Vantaa
Vantaa is a major city in the Helsinki metropolitan area of southern Finland, known for hosting Helsinki Airport and serving as an important commercial and residential hub.
-
C.
Kiekko-Espoo
Kiekko-Espoo is a Finnish ice hockey club based in Espoo that has competed in the country’s top professional leagues under various organizational forms.
-
D.
Helsinki
Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
-
E.
Porvoo
Porvoo is a historic coastal city in southern Finland known for its well-preserved wooden Old Town and medieval cathedral.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32877ff248190886717d3329421a7 |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c28f43988190aa06da8c356b9646 |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:09 a.m.