Triple
T33286111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRRF |
E852183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | refugee response framework |
C27646
|
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: refugee response framework Context triple: [CRRF, instanceOf, refugee response framework]
-
A.
refugee protection framework
chosen
A refugee protection framework is a structured set of laws, policies, and procedures designed to ensure the safety, rights, and durable solutions for individuals fleeing persecution, conflict, or serious human rights violations.
-
B.
refugee resettlement program
A refugee resettlement program is an organized system that supports refugees in safely relocating to a new country and integrating into its society through housing, legal assistance, language training, and other essential services.
-
C.
refugee
A refugee is a person who has been forced to flee their home country due to persecution, conflict, violence, or a well-founded fear of such harm, and seeks safety and protection in another country.
-
D.
humanitarian planning framework
A humanitarian planning framework is a structured approach that guides the assessment, design, implementation, and evaluation of coordinated actions to meet urgent needs and protect the rights of crisis-affected populations.
-
E.
refugee crisis
A refugee crisis is a large-scale, often sudden displacement of people fleeing conflict, persecution, or disaster, overwhelming the capacity of receiving states and humanitarian systems to provide protection and basic needs.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.