Triple
T30929581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Sea States Subregional Co-operation |
E787955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cooperation network |
C10807
|
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: cooperation network Context triple: [Baltic Sea States Subregional Co-operation, instanceOf, cooperation network]
-
A.
collaborative networks
Collaborative networks are interconnected groups of individuals or organizations that share resources, knowledge, and responsibilities to achieve common goals more effectively than they could independently.
-
B.
regional collaborative network
chosen
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
C.
cooperative forum
A cooperative forum is an online or physical space where individuals collaboratively discuss, share resources, and make decisions to achieve common goals in a participatory and mutually supportive manner.
-
D.
inter-agency coordination network
An inter-agency coordination network is a structured system of relationships, processes, and communication channels that enables multiple organizations or agencies to collaboratively plan, share information, and align actions toward common objectives.
-
E.
intergovernmental coordination network
An intergovernmental coordination network is a structured system of relationships, processes, and communication channels that enables multiple governmental entities at different levels or jurisdictions to align policies, share information, and collaborate on common objectives.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:52 p.m.