Triple
T14365364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tête Rousse Glacier |
E356216
|
entity |
| Predicate | floodImpact |
P50010
|
FINISHED |
| Object | destruction in Saint-Gervais-les-Bains valley |
—
|
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: destruction in Saint-Gervais-les-Bains valley | Statement: [Tête Rousse Glacier, floodImpact, destruction in Saint-Gervais-les-Bains valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodImpact Context triple: [Tête Rousse Glacier, floodImpact, destruction in Saint-Gervais-les-Bains valley]
-
A.
floodConsequence
chosen
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
B.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
C.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
D.
hasFloodRiskRelevance
Indicates that something is pertinent to, affects, or is used in assessing the risk or likelihood of flooding.
-
E.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fad48748190a0f34ca4d02f9a3c |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.