Triple
T2167853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau for Humanitarian Assistance (USAID) |
E46951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian assistance agency |
C6
|
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 assistance agency Context triple: [Bureau for Humanitarian Assistance (USAID), instanceOf, humanitarian assistance agency]
-
A.
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.
-
B.
nonprofit organization
chosen
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
C.
umbrella organisation
An umbrella organisation is a central body that unites, coordinates, and represents multiple related groups or entities under a common structure or purpose.
-
D.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
E.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:45 p.m.