Triple
T25096380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Kumamoto earthquakes |
E628599
|
entity |
| Predicate | promptedEmergencyResponse |
P32125
|
FINISHED |
| Object | Government of Japan |
—
|
NE NERFINISHED |
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: Government of Japan | Statement: [2016 Kumamoto earthquakes, promptedEmergencyResponse, Government of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promptedEmergencyResponse Context triple: [2016 Kumamoto earthquakes, promptedEmergencyResponse, Government of Japan]
-
A.
emergencyResponse
chosen
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
-
B.
emergencyProvision
Indicates a temporary measure or resource activated specifically to address urgent or crisis situations.
-
C.
emergencyUse
Indicates that something is being used in response to an urgent or critical situation, typically as a temporary or exceptional measure.
-
D.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
-
E.
promptedAction
Indicates that one entity initiates or triggers another entity to perform a specific action.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.