Triple
T4331092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wireless Emergency Alerts system |
E96748
|
entity |
| Predicate | alertCategory |
P40820
|
FINISHED |
| Object | National alerts |
—
|
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: National alerts | Statement: [Wireless Emergency Alerts system, alertCategory, National alerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alertCategory Context triple: [Wireless Emergency Alerts system, alertCategory, National alerts]
-
A.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
B.
warningType
chosen
Indicates the specific category or classification of a warning associated with an entity or event.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
alertMethod
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
E.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.