Triple

T10926829
Position Surface form Disambiguated ID Type / Status
Subject Server Name Indication extension E258090 entity
Predicate hasSuccessor P78 FINISHED
Object Encrypted Client Hello
Encrypted Client Hello is a TLS 1.3 extension that protects privacy by encrypting most of the ClientHello message, including the server name, to prevent passive observers from learning which site a client is connecting to.
E893544 NE FINISHED

How this triple was built (4 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: Encrypted Client Hello | Statement: [Server Name Indication extension, hasSuccessor, Encrypted Client Hello]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Encrypted Client Hello
Context triple: [Server Name Indication extension, hasSuccessor, Encrypted Client Hello]
  • A. Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
    "Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
  • B. AT-TLS (Application Transparent TLS)
    AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
  • C. TLS heartbeat extension (later deprecated)
    The TLS heartbeat extension was a Transport Layer Security protocol feature designed to keep secure connections alive and test reachability, later becoming widely known for the critical Heartbleed vulnerability that led to its deprecation.
  • D. Server Name Indication extension
    The Server Name Indication (SNI) extension is a TLS protocol feature that allows a client to indicate the hostname it is trying to connect to at the start of the handshake so that the server can present the correct certificate for virtual hosting.
  • E. UTA (Using TLS in Applications)
    UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Encrypted Client Hello
Triple: [Server Name Indication extension, hasSuccessor, Encrypted Client Hello]
Generated description
Encrypted Client Hello is a TLS 1.3 extension that protects privacy by encrypting most of the ClientHello message, including the server name, to prevent passive observers from learning which site a client is connecting to.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Encrypted Client Hello
Target entity description: Encrypted Client Hello is a TLS 1.3 extension that protects privacy by encrypting most of the ClientHello message, including the server name, to prevent passive observers from learning which site a client is connecting to.
  • A. Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
    "Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
  • B. AT-TLS (Application Transparent TLS)
    AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
  • C. TLS heartbeat extension (later deprecated)
    The TLS heartbeat extension was a Transport Layer Security protocol feature designed to keep secure connections alive and test reachability, later becoming widely known for the critical Heartbleed vulnerability that led to its deprecation.
  • D. Server Name Indication extension
    The Server Name Indication (SNI) extension is a TLS protocol feature that allows a client to indicate the hostname it is trying to connect to at the start of the handshake so that the server can present the correct certificate for virtual hosting.
  • E. UTA (Using TLS in Applications)
    UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
  • F. None of above. chosen

Provenance (5 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_69d6aa864ed88190818280ab6791d065 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7709165188190aa30dd08deddade4 completed April 9, 2026, 9:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e217475344819088b44b6efb2df1c8 completed April 17, 2026, 11:19 a.m.
NEDg Description generation batch_69e21d8aea2881908ac8f5225b8739c5 completed April 17, 2026, 11:46 a.m.
NED2 Entity disambiguation (via description) batch_69e21eb18a1881908ded331db89063ed completed April 17, 2026, 11:51 a.m.
Created at: April 8, 2026, 9:22 p.m.