Triple
T3493405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapland |
E73789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative 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: administrative region of Finland Context triple: [Lapland, instanceOf, administrative 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.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
-
D.
region of Denmark
A region of Denmark is a top-level administrative division responsible for coordinating healthcare, regional development, and certain public services across multiple municipalities within its geographic area.
-
E.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.