Triple
T18130311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framework for Action for Food Security and Nutrition in Protracted Crises |
E433990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-binding policy framework |
C28159
|
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: non-binding policy framework Context triple: [Framework for Action for Food Security and Nutrition in Protracted Crises, instanceOf, non-binding policy framework]
-
A.
non-binding international agreement
chosen
A non-binding international agreement is a formal understanding between states or international actors that expresses shared intentions or guidelines without creating legally enforceable obligations under international law.
-
B.
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.
-
C.
non-normative document
A non-normative document is a text that provides guidance, explanation, or examples without establishing mandatory rules, requirements, or standards.
-
D.
non-governmental public body
A non-governmental public body is an organization that, while independent of direct government control, performs functions or provides services of public interest, often operating under public law or with public funding and oversight.
-
E.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.