Triple
T7793004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pärnu |
E180225
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Kemi |
E22392
|
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: Kemi | Statement: [Pärnu, hasTwinTown, Kemi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kemi Context triple: [Pärnu, hasTwinTown, Kemi]
-
A.
Kemi
chosen
Kemi is a coastal town in northern Finland known for its port, paper industry, and popular winter attractions like the SnowCastle.
-
B.
Tumpa
Tumpa is a song featured on the album "Legend of the Sun Virgin."
-
C.
Kemijoki
Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
-
D.
Kemi-Tornio
Kemi-Tornio is a cross-border urban area in northern Finland near the Swedish border, known for its industrial activity and location by the Bothnian Bay.
-
E.
Nokianvirta River
The Nokianvirta River is a waterway in southwestern Finland that flows through the town of Nokia and has historically influenced the region’s settlement and industry.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae938714c8190b89917e6ded004da |
completed | March 30, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb13dbe1f88190bde2c5c76dcfeb8f |
completed | March 31, 2026, 12:22 a.m. |
Created at: March 30, 2026, 4:31 p.m.