Triple
T29016047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POODLE attack |
E737309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport layer security vulnerability |
C55533
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: transport layer security vulnerability Context triple: [POODLE attack, instanceOf, transport layer security vulnerability]
-
A.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
B.
TLS extension
A TLS extension is an optional, standardized addition to the TLS protocol that allows clients and servers to negotiate extra capabilities or parameters (such as supported protocols, server names, or security features) during the handshake.
-
C.
network security protocol
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
D.
Insecure-related topic
An insecure-related topic is any subject, situation, or issue that triggers feelings of self-doubt, vulnerability, or inadequacy in an individual or group.
-
E.
session layer protocol
A session layer protocol is a network communication protocol that establishes, manages, and terminates logical connections (sessions) between applications, handling dialog control, synchronization, and orderly data exchange.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: April 28, 2026, 9:45 a.m.