Triple
T11801004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokkola |
E280624
|
entity |
| Predicate | FinnishName |
P23453
|
FINISHED |
| Object | Kokkola |
E280624
|
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: Kokkola | Statement: [Kokkola, FinnishName, Kokkola]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kokkola Context triple: [Kokkola, FinnishName, Kokkola]
-
A.
Kokkola
chosen
Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
-
B.
Kouvola
Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
-
C.
Kuokkala
Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
-
D.
Kuokkala
Kuokkala is a residential district of the city of Jyväskylä in central Finland, known for its lakeside location and distinctive bridge connection to the city center.
-
E.
Kuopio
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.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a4512c8190b7782e1dee053000 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c1d31048190ab0a8d8e00515211 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 8, 2026, 9:42 p.m.