Triple
T33809638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tihama of Saudi Arabia |
E866488
|
entity |
| Predicate | climateHazard |
P25357
|
FINISHED |
| Object | heat stress risk |
—
|
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: heat stress risk | Statement: [Tihama of Saudi Arabia, climateHazard, heat stress risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateHazard Context triple: [Tihama of Saudi Arabia, climateHazard, heat stress risk]
-
A.
climateEventType
Indicates the specific kind or category of a climate-related event associated with an entity or occurrence.
-
B.
frequentNaturalHazard
chosen
Indicates that a location or area regularly experiences natural hazards such as floods, earthquakes, storms, or similar events with notable frequency.
-
C.
climateChangeEffect
Indicates how climate change influences or alters a particular entity, condition, or process.
-
D.
naturalHazardFunction
Indicates a functional relationship where an entity serves as, causes, or performs the role of a natural hazard (e.g., earthquake, flood, storm) affecting other entities or environments.
-
E.
climateIndicator
Indicates that something serves as a measure or signal of the state, change, or impact of climate-related 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffc4749081908be0bb146eba9685 |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.