Triple

T8489730
Position Surface form Disambiguated ID Type / Status
Subject RFC 8996 E200936 entity
Predicate securityConsideration P25437 FINISHED
Object TLS 1.0 is vulnerable to multiple attacks E39658 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: TLS 1.0 is vulnerable to multiple attacks | Statement: [RFC 8996, securityConsideration, TLS 1.0 is vulnerable to multiple attacks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS 1.0 is vulnerable to multiple attacks
Context triple: [RFC 8996, securityConsideration, TLS 1.0 is vulnerable to multiple attacks]
  • A. TLS 1.0 chosen
    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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69ca831d7b148190a6e32c1de43ab13b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe5596f1c8190aead21a245f21c07 completed March 31, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce3a4e5be48190b5c598123ef75f8b completed April 2, 2026, 9:43 a.m.
Created at: March 30, 2026, 6:13 p.m.