Triple
T7384178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Finland |
E170339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical region of Finland |
C7616
|
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: historical region of Finland Context triple: [Eastern Finland, instanceOf, historical region of Finland]
-
A.
region of Finland
chosen
A region of Finland is an administrative and geographical area that groups together multiple municipalities for purposes of governance, planning, and regional identity.
-
B.
former province of Finland
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.
-
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.
Town in Finland
A Town in Finland is an administratively defined urban municipality that provides local governance, services, and infrastructure within a specific geographic area of the Finnish state.
-
E.
historical region of Ukraine
A historical region of Ukraine is a geographically defined area within present-day Ukraine that is distinguished by its unique historical development, cultural heritage, and traditional boundaries formed over past centuries.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:08 p.m.