Triple
T23233833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecting Europe Facility |
E581232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU programme |
C15070
|
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: EU programme Context triple: [Connecting Europe Facility, instanceOf, EU programme]
-
A.
European Union programme
chosen
A European Union programme is an organized, EU-funded initiative designed to implement specific policies or objectives across member states and partner countries in areas such as research, education, regional development, or social cohesion.
-
B.
European Union programme component
A European Union programme component is a distinct, organized part of an EU-funded programme that contributes specific activities, resources, or objectives toward achieving the programme’s overall goals.
-
C.
European Union funding framework
The European Union funding framework is the structured system of policies, programs, and financial instruments through which the EU allocates budgetary resources to support its strategic objectives across member states and partner regions.
-
D.
implementing body of EU programme
An implementing body of an EU programme is an organization designated to manage, execute, and oversee specific EU-funded activities in accordance with EU rules, objectives, and reporting requirements.
-
E.
European research project
A European research project is a collaborative, often multinational initiative funded or supported by European institutions to advance scientific, technological, or societal knowledge and innovation.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:09 p.m.