Triple
T33003431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Resilience Forum |
E844431
|
entity |
| Predicate | typicalHazardsAddressed |
—
|
GENERATED |
| Object | flooding |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHazardsAddressed Context triple: [Local Resilience Forum, typicalHazardsAddressed, flooding]
-
A.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
C.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
D.
hazardConcentratedAt
Indicates that a hazardous substance or condition is present with elevated intensity or density at a specific location or point.
-
E.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
- F. None of above.
Provenance (1 batch)
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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.