Triple
T31080824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | affectsSoftware |
P170383
|
FINISHED |
| Object | OpenSSL |
—
|
NE NERFINISHED |
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: OpenSSL | Statement: [Heartbleed, affectsSoftware, OpenSSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsSoftware Context triple: [Heartbleed, affectsSoftware, OpenSSL]
-
A.
affectsProgram
Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
-
B.
affectsProduct
chosen
Indicates that one entity has an influence or impact on the state, quality, or outcome of a product.
-
C.
alsoAffects
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
-
D.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
E.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 9:02 p.m.