Triple
T1368227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Flash |
E30049
|
entity |
| Predicate | notableSecurityEvent |
P18677
|
FINISHED |
| Object | frequent critical vulnerabilities reported by security researchers |
—
|
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: frequent critical vulnerabilities reported by security researchers | Statement: [Adobe Flash, notableSecurityEvent, frequent critical vulnerabilities reported by security researchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSecurityEvent Context triple: [Adobe Flash, notableSecurityEvent, frequent critical vulnerabilities reported by security researchers]
-
A.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
-
B.
notableGate
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
-
C.
hasNotableIncident
chosen
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
D.
notableProtectiveFailure
Indicates a relationship where an entity’s protective role or safeguards significantly failed, leading to a notable or consequential breakdown in protection.
-
E.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d497f88190993d16a208ced43d |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.