Triple
T10926898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Fragment Length extension |
E258092
|
entity |
| Predicate | usedIn |
P98
|
FINISHED |
| Object |
TLS ClientHello
TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
|
E893545
|
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: TLS ClientHello | Statement: [Max Fragment Length extension, usedIn, TLS ClientHello]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS ClientHello Context triple: [Max Fragment Length extension, usedIn, TLS ClientHello]
-
A.
ServerHello with extensions
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
B.
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.
-
C.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
D.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
E.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
- 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: TLS ClientHello Triple: [Max Fragment Length extension, usedIn, TLS ClientHello]
Generated description
TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TLS ClientHello Target entity description: TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
-
A.
ServerHello with extensions
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
B.
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.
-
C.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
D.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
E.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
- 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.