Triple
T11701382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuopio Airport |
E278132
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Kuopio |
E357411
|
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: Kuopio | Statement: [Kuopio Airport, serves, Kuopio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuopio Context triple: [Kuopio Airport, serves, Kuopio]
-
A.
Kuopio
chosen
Kuopio is a city in eastern Finland known for its lakeside setting, vibrant cultural life, and status as a regional center for education and commerce.
-
B.
Kouvola
Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
-
C.
Kokkola
Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
-
D.
Oulu
Oulu is a major city in northern Finland known for its technology industry, university, and position near the Gulf of Bothnia.
-
E.
Joensuu
Joensuu is a city in eastern Finland that serves as a regional center for North Karelia, known for its university, forestry industry, and proximity to lakes and forests.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49a025881909377c81d3debf465 |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb63c80048190be87b41cdd4ac775 |
completed | May 7, 2026, 3:56 p.m. |
Created at: April 8, 2026, 9:40 p.m.