Triple
T35140392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOM Programme and Budget |
E1014688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational budget document |
C12023
|
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: organizational budget document Context triple: [IOM Programme and Budget, instanceOf, organizational budget document]
-
A.
UN specialized agency budget document
chosen
A UN specialized agency budget document is an official financial plan that details the projected income, expenditures, and resource allocations of a specific UN specialized agency for a defined period, typically approved by its governing bodies.
-
B.
budgetary framework
A budgetary framework is a structured system of rules, processes, and assumptions that guides how financial resources are planned, allocated, monitored, and controlled over a specific period.
-
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.
budgetary fund
A budgetary fund is a pool of financial resources allocated and tracked within a formal budget to support specific programs, projects, or organizational objectives.
-
E.
strategic document
A strategic document is a formal written plan that outlines an organization’s long-term goals, priorities, and actions for achieving its mission and competitive advantage.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.