Triple
T27692270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS heartbeat extension |
E698189
|
entity |
| Predicate | notableImplementationBug |
P21734
|
FINISHED |
| Object | OpenSSL Heartbleed bug |
—
|
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 Heartbleed bug | Statement: [TLS heartbeat extension, notableImplementationBug, OpenSSL Heartbleed bug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableImplementationBug Context triple: [TLS heartbeat extension, notableImplementationBug, OpenSSL Heartbleed bug]
-
A.
notableException
Indicates that something or someone stands out as an unusual or noteworthy deviation from an expected pattern, rule, or general case.
-
B.
notableEarlyIssue
Indicates that the subject is a significant or noteworthy early edition, release, or version of the object.
-
C.
knownIssue
chosen
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
D.
notWellDocumented
Indicates that the subject lacks sufficient, clear, or comprehensive documentation.
-
E.
notableExceptionArea
Indicates that a specific area is recognized as an exception to a general rule, pattern, or classification that applies elsewhere.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: April 27, 2026, 2:52 p.m.