Triple
T27840536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falco |
E703664
|
entity |
| Predicate | alertsOn |
P23340
|
FINISHED |
| Object | suspicious activity in containers |
—
|
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: suspicious activity in containers | Statement: [Falco, alertsOn, suspicious activity in containers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alertsOn Context triple: [Falco, alertsOn, suspicious activity in containers]
-
A.
alertSystem
chosen
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
B.
providesAlertsTo
Indicates that one entity sends or delivers alerts or notifications to another entity.
-
C.
alertMethod
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
D.
alarmSignal
Indicates that an alarm or warning signal is being emitted, triggered, or active in response to some condition or event.
-
E.
notificationType
Indicates the specific category or kind of notification associated with an event or 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d4944c8190b2306590c9ea65d2 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:02 p.m.