Triple

T311106
Position Surface form Disambiguated ID Type / Status
Subject HTTPS E7608 entity
Predicate definedIn P775 FINISHED
Object RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
E40278 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: RFC 2818 | Statement: [HTTPS, definedIn, RFC 2818]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2818
Context triple: [HTTPS, definedIn, RFC 2818]
  • A. RFC 8446
    RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
  • B. RFC 5246
    RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
  • C. RFC 2246
    RFC 2246 is the original specification of the Transport Layer Security (TLS) protocol version 1.0, defining the foundational standard for securing communications over computer networks.
  • D. RFC 4346
    RFC 4346 is the Internet Engineering Task Force (IETF) specification that defines Transport Layer Security (TLS) version 1.1, a cryptographic protocol for securing communications over computer networks.
  • E. RFC 8017
    RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
  • 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: RFC 2818
Triple: [HTTPS, definedIn, RFC 2818]
Generated description
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 2818
Target entity description: RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
  • A. RFC 8446
    RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
  • B. RFC 5246
    RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
  • C. RFC 2246
    RFC 2246 is the original specification of the Transport Layer Security (TLS) protocol version 1.0, defining the foundational standard for securing communications over computer networks.
  • D. RFC 4346
    RFC 4346 is the Internet Engineering Task Force (IETF) specification that defines Transport Layer Security (TLS) version 1.1, a cryptographic protocol for securing communications over computer networks.
  • E. RFC 8017
    RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea49636c8190a69cbd951fc0a4db completed Feb. 28, 2026, 1:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3bc277528819096184b6cc6b98ae2 completed March 1, 2026, 4:10 a.m.
NEDg Description generation batch_69a3bea16ee48190a033ea3907703e40 completed March 1, 2026, 4:20 a.m.
NED2 Entity disambiguation (via description) batch_69a3befc80a8819092506dd29e18f2aa completed March 1, 2026, 4:22 a.m.
Created at: Feb. 28, 2026, 1:07 p.m.