Triple
T33423877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Ecuador earthquake |
E855916
|
entity |
| Predicate | emergencyType |
P32124
|
FINISHED |
| Object | state of emergency |
—
|
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: state of emergency | Statement: [2016 Ecuador earthquake, emergencyType, state of emergency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyType Context triple: [2016 Ecuador earthquake, emergencyType, state of emergency]
-
A.
emergency
Indicates that an entity is in a state of urgent danger or critical need that requires immediate attention or action.
-
B.
emergencyConcern
Indicates a relationship where one entity has an urgent, high-priority concern or issue about another entity or situation that may require immediate attention or action.
-
C.
emergencyTypesCovered
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
D.
emergencyUse
Indicates that something is being used in response to an urgent or critical situation, typically as a temporary or exceptional measure.
-
E.
emergencyEvent
chosen
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.