Triple
T10024766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object |
Upgrading to TLS Within HTTP/1.1
"Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
|
E835149
|
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: Upgrading to TLS Within HTTP/1.1 | Statement: [RFC 2817, title, Upgrading to TLS Within HTTP/1.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Upgrading to TLS Within HTTP/1.1 Context triple: [RFC 2817, title, Upgrading to TLS Within HTTP/1.1]
-
A.
Deprecating TLS 1.0 and TLS 1.1
"Deprecating TLS 1.0 and TLS 1.1" is an IETF standards-track document that formally declares the older TLS 1.0 and 1.1 protocol versions obsolete and recommends their removal from use in favor of more secure versions like TLS 1.2 and 1.3.
-
B.
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.
-
C.
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.
-
D.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
E.
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.
- 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: Upgrading to TLS Within HTTP/1.1 Triple: [RFC 2817, title, Upgrading to TLS Within HTTP/1.1]
Generated description
"Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Upgrading to TLS Within HTTP/1.1 Target entity description: "Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
-
A.
Deprecating TLS 1.0 and TLS 1.1
"Deprecating TLS 1.0 and TLS 1.1" is an IETF standards-track document that formally declares the older TLS 1.0 and 1.1 protocol versions obsolete and recommends their removal from use in favor of more secure versions like TLS 1.2 and 1.3.
-
B.
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.
-
C.
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.
-
D.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
E.
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.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7d9c9c81909a0a0917deed0973 |
completed | April 2, 2026, 1:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26ac2f14081908deaf3945491af78 |
completed | April 5, 2026, 1:59 p.m. |
| NEDg | Description generation | batch_69d26b9212108190bb3cbb6c4c76073f |
completed | April 5, 2026, 2:02 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d26c10eae88190a972fdb7425fd01a |
completed | April 5, 2026, 2:05 p.m. |
Created at: March 30, 2026, 8:53 p.m.