Triple
T6228301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Maitri |
E139289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian 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: humanitarian relief operation Context triple: [Operation Maitri, instanceOf, humanitarian relief operation]
-
A.
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.
-
B.
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.
-
C.
country-level humanitarian fund
A country-level humanitarian fund is a pooled financing mechanism that channels resources to support timely, coordinated, and flexible humanitarian response within a specific country.
-
D.
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.
-
E.
humanitarian emblem
A humanitarian emblem is a universally recognized protective symbol used in armed conflicts and emergencies to identify and safeguard medical services, relief personnel, and facilities under international humanitarian law.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:22 p.m.