Triple
T37828301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ShakeAlert earthquake early warning system |
E943124
|
entity |
| Predicate | alertDeliveryChannel |
P7414
|
FINISHED |
| Object | mobile devices |
—
|
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: mobile devices | Statement: [ShakeAlert earthquake early warning system, alertDeliveryChannel, mobile devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alertDeliveryChannel Context triple: [ShakeAlert earthquake early warning system, alertDeliveryChannel, mobile devices]
-
A.
alertMethod
chosen
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
B.
providesAlertsTo
Indicates that one entity sends or delivers alerts or notifications to another entity.
-
C.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
D.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
E.
warningRecipient
Indicates that one entity is the recipient or target audience of a warning issued by another entity.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.