Triple
T6730015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Pegasus |
E153610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | relief operation |
C19445
|
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: relief operation Context triple: [Operation Pegasus, instanceOf, relief operation]
-
A.
humanitarian relief operation
chosen
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.
-
B.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
-
C.
rescue mission
A rescue mission is a coordinated operation undertaken to locate, assist, and safely extract individuals or groups from dangerous or life-threatening situations.
-
D.
crisis response organization
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
-
E.
refugee assistance organization
A refugee assistance organization is an entity that provides protection, resources, and support services to individuals and families displaced from their home countries due to conflict, persecution, or disaster, helping them meet basic needs and rebuild their lives.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:09 p.m.