Triple
T22396472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorabari Glacier |
E553643
|
entity |
| Predicate | associatedWithDisaster |
P15089
|
FINISHED |
| Object | 2013 Uttarakhand floods |
—
|
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: 2013 Uttarakhand floods | Statement: [Chorabari Glacier, associatedWithDisaster, 2013 Uttarakhand floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDisaster Context triple: [Chorabari Glacier, associatedWithDisaster, 2013 Uttarakhand floods]
-
A.
hasDisaster
chosen
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
C.
impactOfDisasters
Indicates the effects or consequences that disasters have on entities, conditions, or outcomes.
-
D.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
E.
disasterLocation
Indicates the place where a disaster occurs or has its primary impact.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585e84b081908c95ed3e0d987ed8 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.