Triple
T35140391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOM Programme and Budget |
E1014688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | core planning and financial framework document |
C28509
|
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: core planning and financial framework document Context triple: [IOM Programme and Budget, instanceOf, core planning and financial framework document]
-
A.
budgetary framework
chosen
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.
-
B.
architectural planning document
An architectural planning document is a formal artifact that captures and communicates the intended structure, components, constraints, and design decisions of a system or building before implementation or construction begins.
-
C.
strategic priorities framework
A strategic priorities framework is a structured model that helps organizations identify, rank, and align their most important goals and initiatives to guide decision-making and resource allocation.
-
D.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
E.
foundational framework agreement
A foundational framework agreement is a high-level, overarching contract that establishes the core principles, structures, and long-term terms under which more detailed or specific agreements will be developed and executed.
- 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.