Triple
T18050383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key Action 2 |
E431913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Erasmus+ key action |
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: Erasmus+ key action Context triple: [Key Action 2, instanceOf, Erasmus+ key action]
-
A.
European Union education and training program component
A European Union education and training program component is a specific initiative, module, or activity designed and funded within an EU framework to support learning, skills development, and mobility objectives for targeted participants.
-
B.
European higher education instrument
A European higher education instrument is a policy, program, or funding mechanism designed to shape, support, or coordinate higher education systems and institutions across European countries.
-
C.
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.
-
D.
European Union funding action
A European Union funding action is a structured financial support measure provided by EU institutions to co-finance projects, programs, or initiatives that advance the Union’s policy objectives and priorities.
-
E.
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.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:25 a.m.