Triple
T11609013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Cattle Killing of 1856–1857 |
E275334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | famine-related disaster |
C223
|
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: famine-related disaster Context triple: [Great Cattle Killing of 1856–1857, instanceOf, famine-related disaster]
-
A.
famine museum
A famine museum is a cultural institution dedicated to preserving, interpreting, and educating the public about the causes, experiences, and consequences of historical famines through artifacts, exhibits, and personal narratives.
-
B.
famine memorial
A famine memorial is a public monument or installation dedicated to commemorating the victims and historical impact of a specific famine, often serving as a place for reflection, mourning, and education.
-
C.
disaster
chosen
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
D.
agricultural crisis
An agricultural crisis is a severe disruption in farming systems and food production, typically caused by factors such as extreme weather, pests, disease, market shocks, or policy failures, leading to widespread economic hardship and food insecurity.
-
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.
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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.