Triple
T29016090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POODLE attack |
E737309
|
entity |
| Predicate | affectedSoftware |
P79628
|
FINISHED |
| Object | web browsers that supported SSL 3.0 |
—
|
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: web browsers that supported SSL 3.0 | Statement: [POODLE attack, affectedSoftware, web browsers that supported SSL 3.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedSoftware Context triple: [POODLE attack, affectedSoftware, web browsers that supported SSL 3.0]
-
A.
affectedProject
Indicates that one entity has an impact on, or is influenced by, a particular project.
-
B.
affectsProgram
Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
-
C.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
D.
targetedSoftware
chosen
Indicates that a particular piece of software is the specific focus or target of an action, operation, or effect.
-
E.
affectedProjectType
Indicates the type or category of project that is impacted or influenced by a given action, event, or condition.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 9:45 a.m.