Triple
T15876383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cox’s Bazar refugee camps |
E384962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian settlement |
C13673
|
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: humanitarian settlement Context triple: [Cox’s Bazar refugee camps, instanceOf, humanitarian settlement]
-
A.
refugee camp
chosen
A refugee camp is a temporary settlement established to provide shelter, basic services, and protection to people who have been forced to flee their homes due to conflict, persecution, or disaster.
-
B.
humanitarian initiative
A humanitarian initiative is an organized effort or program designed to alleviate human suffering, protect human rights, and improve the well-being of vulnerable or crisis-affected populations.
-
C.
humanitarian protection status
Humanitarian protection status is a legal or administrative designation granted to individuals who cannot safely return to their home country, providing them with temporary or long-term protection, basic rights, and access to essential services.
-
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 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.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.