Triple
T876261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Development Assistance Framework |
E18924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-year planning document |
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: multi-year planning document Context triple: [United Nations Development Assistance Framework, instanceOf, multi-year planning document]
-
A.
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.
-
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.
planning library
A planning library is a reusable collection of algorithms, data structures, and tools that support the creation, evaluation, and optimization of plans or schedules within software applications.
-
D.
magisterial document
A magisterial document is an official teaching text issued by the authority of the Church’s magisterium to articulate, clarify, or develop doctrine and moral guidance for the faithful.
-
E.
United States presidential reorganization plan
A United States presidential reorganization plan is a formal proposal submitted by the President to Congress to restructure, consolidate, or transfer functions within the executive branch to improve its efficiency and effectiveness.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.