Triple
T20064520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Finland |
E499573
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kotka |
—
|
NE NERFINISHED |
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: Kotka | Statement: [Southeastern Finland, contains, Kotka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kotka Context triple: [Southeastern Finland, contains, Kotka]
-
A.
Kotka
chosen
Kotka is a coastal city in southeastern Finland on the Gulf of Finland, known as an important port and maritime center.
-
B.
Kajaani
Kajaani is a small city in central Finland known for its historic castle ruins and role as a regional cultural and economic center in the Kainuu region.
-
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.
Janakkala
Janakkala is a municipality in southern Finland known for its rural landscapes and historical churches, located within the Kanta-Häme region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663787190819096b2b78b38c1bf12 |
completed | April 20, 2026, 5:33 p.m. |
Created at: April 11, 2026, 3:39 p.m.