Triple
T26509107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Nepal earthquake |
E669629
|
entity |
| Predicate | casualtiesDead |
P62746
|
FINISHED |
| Object | over 8,900 people |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: over 8,900 people | Statement: [2015 Nepal earthquake, casualtiesDead, over 8,900 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesDead Context triple: [2015 Nepal earthquake, casualtiesDead, over 8,900 people]
-
A.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
B.
militaryDeaths
Indicates the number of individuals who died while serving in a military capacity, typically during armed conflict or related operations.
-
C.
casualtiesTotal
Indicates the total number of people killed and injured as a result of a particular event or incident.
-
D.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
E.
casualtiesKilledAndMortallyWounded
chosen
Indicates that the relationship records the number of individuals who were killed outright or died later from mortal wounds.
- F. None of above.
Provenance (3 batches)
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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:18 a.m.