Triple
T29338652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Disaster Mitigation Funds |
E743977
|
entity |
| Predicate | riskTypesAddressed |
P28689
|
FINISHED |
| Object | 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: floods | Statement: [State Disaster Mitigation Funds, riskTypesAddressed, floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskTypesAddressed Context triple: [State Disaster Mitigation Funds, riskTypesAddressed, floods]
-
A.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
B.
riskAddressed
chosen
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
-
C.
riskTypesManaged
Indicates that one entity is responsible for handling, controlling, or overseeing specific categories of risk associated with another entity or context.
-
D.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
E.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669255db48190a9541c77cb9b5ede |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:32 p.m.