Triple
T8808884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyland |
E209603
|
entity |
| Predicate | containsCityHistorically |
P3786
|
FINISHED |
| Object | Loviisa |
E307202
|
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: Loviisa | Statement: [Nyland, containsCityHistorically, Loviisa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loviisa Context triple: [Nyland, containsCityHistorically, Loviisa]
-
A.
Loviisa
chosen
Loviisa is a small coastal town and municipality in southern Finland known for its historic wooden houses, seaside location, and nuclear power plant.
-
B.
Ylivieska
Ylivieska is a small town in Northern Ostrobothnia, Finland, known as a regional commercial and service center along the Kalajoki River.
-
C.
Sotkamo
Sotkamo is a municipality in eastern Finland known for its mining industry, outdoor recreation, and the popular Vuokatti ski and sports resort area.
-
D.
Imatra
Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
-
E.
Lempäälä
Lempäälä is a municipality in the Pirkanmaa region of southern Finland, known for its lakeside landscapes and proximity to the city of Tampere.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd4cbec8190a929d4e60da8ad65 |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d32a1e1de88190a98ce4b6aea1a148 |
completed | April 6, 2026, 3:35 a.m. |
Created at: March 30, 2026, 6:45 p.m.