Triple
T22344904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åland in Nordic and Baltic regional cooperation |
E552367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Nordic cooperation |
C12796
|
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: component of Nordic cooperation Context triple: [Åland in Nordic and Baltic regional cooperation, instanceOf, component of Nordic cooperation]
-
A.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
B.
regional cooperation bloc
chosen
A regional cooperation bloc is an alliance of neighboring countries that coordinate policies and collaborate on economic, political, or security issues to advance shared regional interests.
-
C.
Nordic tradition
Nordic tradition encompasses the customs, beliefs, rituals, and cultural practices that have developed over centuries in the Nordic countries, shaped by their history, mythology, climate, and social values.
-
D.
Nordic-level political organization
A Nordic-level political organization is a transnational body that coordinates and promotes political cooperation, policy alignment, and shared values among the Nordic countries.
-
E.
Norwegian foundation
A Norwegian foundation is a legally independent, non-profit entity in Norway that manages assets dedicated to specific public-benefit, charitable, cultural, or private purposes according to a founding document and national regulations.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.