Triple

T4979793
Position Surface form Disambiguated ID Type / Status
Subject RFC 7465 E111854 entity
Predicate securityConsideration P25437 FINISHED
Object RC4 is no longer considered secure for TLS E20655 NE FINISHED

How this triple was built (2 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: RC4 is no longer considered secure for TLS | Statement: [RFC 7465, securityConsideration, RC4 is no longer considered secure for TLS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RC4 is no longer considered secure for TLS
Context triple: [RFC 7465, securityConsideration, RC4 is no longer considered secure for TLS]
  • A. RC4 stream cipher chosen
    The RC4 stream cipher is a once-widely used symmetric key algorithm known for its simplicity and speed in software, but now considered insecure due to multiple discovered vulnerabilities.
  • B. RFC 7465 (prohibition in TLS)
    RFC 7465 is an Internet standards document that formally prohibits the use of the RC4 stream cipher in Transport Layer Security (TLS) due to its significant cryptographic weaknesses.
  • C. RFC 6176 (prohibition of SSL 2.0)
    RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally deprecates and forbids the use of the insecure SSL 2.0 protocol in favor of more secure TLS versions.
  • D. RC2
    RC2 is a symmetric-key block cipher designed by cryptographer Ronald L. Rivest and widely used in early Internet security applications.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd441adc208190b70a033a0741d01e completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd723418e881908f1e43b1be0a2f17 completed March 20, 2026, 4:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a0f90048190998dad99555891c0 completed March 21, 2026, 12:07 p.m.
Created at: March 20, 2026, 1:33 p.m.