Triple
T34864621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroregions |
E1004977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European regional cooperation mechanism |
C14427
|
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: European regional cooperation mechanism Context triple: [Euroregions, instanceOf, European regional cooperation mechanism]
-
A.
European Union mechanism
A European Union mechanism is a structured process, instrument, or framework established by EU institutions to implement, coordinate, or enforce common policies and objectives across member states.
-
B.
European Union development strategy
The European Union development strategy is a coordinated framework of policies, funding instruments, and long-term goals designed to promote sustainable economic growth, social cohesion, environmental protection, and global partnerships within the EU and with partner countries.
-
C.
European Union policy region
A European Union policy region is a designated territorial unit within EU member states used for implementing, managing, and evaluating EU policies, funding programs, and statistical analyses.
-
D.
European organisation
chosen
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
-
E.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.