Triple
T31994819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional State Administrative Agencies (in internal security matters) |
E816966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Finnish regional authority |
C60076
|
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: Finnish regional authority Context triple: [Regional State Administrative Agencies (in internal security matters), instanceOf, Finnish regional authority]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
protected area of Finland
A protected area of Finland is a geographically defined region designated and managed under Finnish law to conserve biodiversity, natural landscapes, and cultural heritage, restricting human activities to ensure long-term environmental protection.
- F. None of above. chosen
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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:13 a.m.