Triple
T10848863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | multiannual financial framework of the European Union |
E256087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-term budget framework |
C2953
|
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: long-term budget framework Context triple: [multiannual financial framework of the European Union, instanceOf, long-term budget framework]
-
A.
long-term plan
A long-term plan is a structured, forward-looking strategy that outlines major goals and the sequence of actions needed to achieve them over an extended period of time.
-
B.
multiannual funding programme
chosen
A multiannual funding programme is a structured financial initiative that allocates resources over several years to support specified objectives, projects, or policy priorities within a defined framework and timeline.
-
C.
budgetary planning exercise
A budgetary planning exercise is a structured activity in which individuals or organizations forecast income and expenses over a specific period to allocate resources, evaluate trade-offs, and ensure financial goals are achievable.
-
D.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
-
E.
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.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.