Triple
T32953239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Finland Province |
E843017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative province of Finland |
C8509
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former administrative province of Finland Context triple: [Western Finland Province, instanceOf, former administrative province of Finland]
-
A.
former province of Finland
chosen
A former province of Finland is an administrative region that existed under Finland’s historical provincial system but has since been reorganized or abolished in later territorial reforms.
-
B.
historical province of Finland
A historical province of Finland is a traditional regional division reflecting former administrative, cultural, and historical boundaries that shaped Finnish identity before modern administrative reforms.
-
C.
historical province of Sweden
A historical province of Sweden is a traditional geographic and cultural region with historical significance, distinct identity, and often unique customs, which no longer serves as an administrative unit but remains important in cultural and regional contexts.
-
D.
former municipality of Finland
A former municipality of Finland is an administrative region that once functioned as an independent local government unit but has since been merged with or incorporated into another municipality.
-
E.
region of Finland
A region of Finland is an administrative and geographical area that groups together multiple municipalities for purposes of governance, planning, and regional identity.
- F. None of above.
Provenance (1 batch)
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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:21 a.m.