Triple
T10926887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Fragment Length extension |
E258092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Transport Layer Security feature |
C25115
|
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 feature Context triple: [Max Fragment Length extension, instanceOf, Transport Layer Security feature]
-
A.
TLS extension
chosen
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.
-
B.
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.
-
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.
Bluetooth Low Energy security feature
A Bluetooth Low Energy security feature is a mechanism or protocol that protects BLE communications by providing authentication, encryption, integrity, and privacy between connected devices.
-
E.
U.S. government encryption standard
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
- F. None of above.
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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.