Triple
T9922313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic hurricane season |
E187824
|
entity |
| Predicate | typicalPreparednessAction |
P74331
|
FINISHED |
| Object | evacuation planning |
—
|
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: evacuation planning | Statement: [Atlantic hurricane season, typicalPreparednessAction, evacuation planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPreparednessAction Context triple: [Atlantic hurricane season, typicalPreparednessAction, evacuation planning]
-
A.
emergencyPlanningFocus
chosen
Indicates that the primary emphasis or subject of emergency planning activities is directed toward a particular entity or aspect.
-
B.
cityPreparedFor
Indicates that a city has made the necessary plans, provisions, or arrangements to be ready for a particular event, situation, or condition.
-
C.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
-
D.
declaredEmergency
Indicates that an official authority has formally announced an emergency situation is in effect.
-
E.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb56c7da88190ac37986a2e766b1e |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.