Triple

T2114613
Position Surface form Disambiguated ID Type / Status
Subject RFC 6176 E42577 entity
Predicate deprecates P32017 FINISHED
Object SSL 2.0 E6788 NE FINISHED

How this triple was built (3 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: SSL 2.0 | Statement: [RFC 6176, deprecates, SSL 2.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSL 2.0
Context triple: [RFC 6176, deprecates, SSL 2.0]
  • A. SSL 2.0 chosen
    SSL 2.0 is an early, now-obsolete version of the Secure Sockets Layer protocol that provided encrypted communication over networks before being replaced by more secure successors like TLS.
  • B. SSL 3.0
    SSL 3.0 is an obsolete cryptographic protocol that once secured internet communications and served as the foundation for the early versions of TLS.
  • C. TLS 1.0
    TLS 1.0 is an early version of the Transport Layer Security protocol used to secure communications over computer networks, now largely deprecated in favor of more secure later versions.
  • 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. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deprecates
Context triple: [RFC 6176, deprecates, SSL 2.0]
  • A. deprecatedInRFC chosen
    Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
  • B. usedInsteadOf
    Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
  • C. decliningAs
    Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
  • D. deprecatedYear
    Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
  • E. deactivated
    Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
  • F. None of above.

Provenance (4 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_69a8871040f08190aac2e2d0ab6b47ad completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbb05b51c81908a78c816f492c45c completed March 7, 2026, 5:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae58cd22c8819096dfd06d16703bf8 completed March 9, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69abb7ba08948190a3c236bb53ee4257 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.