Triple
T13253786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nurmijärvi |
E315603
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Karkkila |
E840108
|
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: Karkkila | Statement: [Nurmijärvi, hasBorderWith, Karkkila]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karkkila Context triple: [Nurmijärvi, hasBorderWith, Karkkila]
-
A.
Karkkila
chosen
Karkkila is a small town and municipality in southern Finland known for its industrial history and surrounding lakes and forests.
-
B.
Kärkölä
Kärkölä is a small municipality in southern Finland known for its rural character and historical ties to notable Finnish figures.
-
C.
Karttula
Karttula is a small former municipality in eastern Finland, known for its rural landscapes and location within the Northern Savonia region.
-
D.
Karhula
Karhula is a former Finnish municipality and industrial community that was incorporated into the city of Kotka.
-
E.
Tikkakoski
Tikkakoski is a district in Jyväskylä, Finland, known for its military air base and role as a key center for the Finnish Air Force.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f7517048190b4eac4e44e81ff66 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794202df08190acf1a7710b64198c |
completed | May 3, 2026, 6:29 p.m. |
Created at: April 9, 2026, 9:24 p.m.