Triple

T338870
Position Surface form Disambiguated ID Type / Status
Subject SSL 2.0 E6788 entity
Predicate precedes P97 FINISHED
Object SSL 3.0 E5907 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: SSL 3.0 | Statement: [SSL 2.0, precedes, SSL 3.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSL 3.0
Context triple: [SSL 2.0, precedes, SSL 3.0]
  • A. SSL 3.0 chosen
    SSL 3.0 is an obsolete cryptographic protocol that once secured internet communications and served as the foundation for the early versions of TLS.
  • B. SSL 2.0
    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.
  • 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.

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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eae3a27c81909fc7deb600125fb1 completed Feb. 28, 2026, 1:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3d4e56b448190aac66218417e95b8 completed March 1, 2026, 5:55 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.