Triple
T21188248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Quick Reaction Alert (South) |
E522141
|
entity |
| Predicate | alertStatus |
P79833
|
FINISHED |
| Object | 24/7 |
—
|
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: 24/7 | Statement: [UK Quick Reaction Alert (South), alertStatus, 24/7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alertStatus Context triple: [UK Quick Reaction Alert (South), alertStatus, 24/7]
-
A.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
B.
alertMethod
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
C.
activationStatus
chosen
Indicates whether an entity is currently active, enabled, or in effect within a given context.
-
D.
alarmSignal
Indicates that an alarm or warning signal is being emitted, triggered, or active in response to some condition or event.
-
E.
threatStatusSystem
Indicates the classification framework or system used to assign a conservation or threat status to an 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333403448190bcd9cc0805e414b5 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.