Triple
T30796159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Defence and Emergency Management |
E784233
|
entity |
| Predicate | typeOfHazards |
P1950
|
FINISHED |
| Object | natural hazards |
—
|
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: natural hazards | Statement: [Civil Defence and Emergency Management, typeOfHazards, natural hazards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHazards Context triple: [Civil Defence and Emergency Management, typeOfHazards, natural hazards]
-
A.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
C.
isHazard
Indicates that something poses a potential risk, danger, or harmful condition to people, property, or the environment.
-
D.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 29, 2026, 8:42 p.m.