Triple
T6839012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIDO Programme and Budget document |
E157522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planning and budgeting 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: planning and budgeting document Context triple: [UNIDO Programme and Budget document, instanceOf, planning and budgeting document]
-
A.
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.
-
B.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
C.
planning department
A planning department is an organizational unit responsible for developing, coordinating, and overseeing plans, policies, and resource allocation to achieve strategic and operational goals.
-
D.
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.
-
E.
financial policy document
A financial policy document is an official written guideline that defines an organization’s principles, rules, and procedures for managing, controlling, and reporting its financial activities.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:19 p.m.