Triple
T16688667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth of Bavaria |
E405534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Humanitarian |
C38241
|
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 Context triple: [Elisabeth of Bavaria, instanceOf, Humanitarian]
-
A.
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.
-
B.
humanitarian organizations
Humanitarian organizations are entities that provide impartial aid, protection, and support to people affected by crises, disasters, and poverty, aiming to alleviate suffering and uphold human dignity.
-
C.
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.
-
D.
humanitarian health organization
A humanitarian health organization is an entity that delivers medical care, public health services, and health-related support to vulnerable or crisis-affected populations, prioritizing equity, neutrality, and rapid response to human suffering.
-
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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.