Triple
T15196649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Øresund Committee |
E363153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border political cooperation body |
C15734
|
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: cross-border political cooperation body Context triple: [Øresund Committee, instanceOf, cross-border political cooperation body]
-
A.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
B.
regional cooperation bloc
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.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
D.
cross-border institution
chosen
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
-
E.
inter-parliamentary organization
An inter-parliamentary organization is a cooperative body composed of members from the legislatures of multiple countries, established to promote dialogue, coordination, and collaboration on shared political, legal, and policy issues.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:10 a.m.