Triple
T4420723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian Response Plan |
E95090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic response document |
C5025
|
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: strategic response document Context triple: [Humanitarian Response Plan, instanceOf, strategic response 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.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
-
C.
reference document
A reference document is an organized, authoritative source of information designed to be consulted as needed for specific facts, standards, or procedures rather than read sequentially.
-
D.
United Nations strategic planning framework
chosen
The United Nations strategic planning framework is a structured, organization-wide approach that aligns UN mandates, goals, resources, and performance measures to guide coherent, long-term action across agencies and member states.
-
E.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:30 p.m.