Triple
T7537509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temporary Protected Status |
E178186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian protection status |
C22853
|
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 protection status Context triple: [Temporary Protected Status, instanceOf, humanitarian protection status]
-
A.
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.
-
B.
humanitarian information service
A humanitarian information service is a system that collects, manages, and disseminates critical, reliable information to support decision-making and coordination in humanitarian crises.
-
C.
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.
-
D.
refugee camp
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.
-
E.
humanitarian relief operation
A humanitarian relief operation is a coordinated effort to rapidly provide essential aid, services, and protection to populations affected by crises such as natural disasters, conflicts, or epidemics, aiming to save lives, alleviate suffering, and support basic human dignity.
- F. None of above. chosen
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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:48 p.m.