Triple
T17997565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union policy |
E430542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supranational policy framework |
C2120
|
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: supranational policy framework Context triple: [European Union policy, instanceOf, supranational policy framework]
-
A.
supranational policy
Supranational policy is a set of rules and decisions created by an authority above individual nation-states that member countries agree to follow, often ceding some sovereignty to achieve common goals.
-
B.
supranational entity
A supranational entity is an organization or institution formed by multiple sovereign states that delegates certain decision-making powers above the national level to pursue common policies or goals.
-
C.
national policy framework
A national policy framework is a structured set of overarching principles, goals, and guidelines that coordinate and align government actions, laws, and programs across sectors to achieve long-term national objectives.
-
D.
European Union policy framework
chosen
The European Union policy framework is the overarching system of treaties, institutions, laws, and coordinated strategies through which EU member states collectively design, implement, and enforce policies across economic, social, environmental, and security domains.
-
E.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
Created at: April 10, 2026, 10:23 a.m.