Triple
T9062452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Resilience and Emergency Management |
E217158
|
entity |
| Predicate | typeOfEmergencyAddressed |
P77203
|
FINISHED |
| Object | natural disasters |
—
|
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 disasters | Statement: [Office of Resilience and Emergency Management, typeOfEmergencyAddressed, natural disasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEmergencyAddressed Context triple: [Office of Resilience and Emergency Management, typeOfEmergencyAddressed, natural disasters]
-
A.
typeOfEmergencyService
Indicates the specific category or kind of emergency service associated with or provided in a given situation.
-
B.
emergencyTypesCovered
chosen
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
C.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
-
D.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
E.
emergencyAlertType
Indicates the specific category or kind of emergency associated with an alert.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ecd352c8190a744579209b2e535 |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.