Triple
T18456221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Ostrobothnia |
E450908
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Raahe |
—
|
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: Raahe | Statement: [Northern Ostrobothnia, hasMunicipality, Raahe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raahe Context triple: [Northern Ostrobothnia, hasMunicipality, Raahe]
-
A.
Raahe
chosen
Raahe is a coastal town in northern Finland known for its maritime heritage and strategic location on the Gulf of Bothnia.
-
B.
Kerava
Kerava is a small city in southern Finland known as a commuter town within the Greater Helsinki region.
-
C.
Imatra
Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
-
D.
Lappeenranta
Lappeenranta is a city in southeastern Finland near the Russian border, known for its lakeside location on Saimaa and its role as a regional commercial and educational center.
-
E.
Kirkee
Kirkee is a cantonment town near Pune in Maharashtra, India, historically notable as the site of a major Anglo-Maratha War battle.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264c10408190b2085ade88655c7d |
completed | April 19, 2026, 7 p.m. |
Created at: April 10, 2026, 11:31 a.m.