Triple

T28397134
Position Surface form Disambiguated ID Type / Status
Subject TLS DHE ciphersuites E719310 entity
Predicate exampleCipherSuite P76795 FINISHED
Object TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 LITERAL 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_DHE_RSA_WITH_AES_128_GCM_SHA256 | Statement: [TLS DHE ciphersuites, exampleCipherSuite, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: exampleCipherSuite
Context triple: [TLS DHE ciphersuites, exampleCipherSuite, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256]
  • A. supportsCipherSuite
    Indicates that one entity is capable of using or handling a specified cryptographic cipher suite in secure communications.
  • B. cipherSuiteIdentifier chosen
    Indicates the specific cryptographic cipher suite used or referenced in a communication or security context.
  • C. cipherSuiteNamePrefix
    Indicates that one entity specifies a prefix string that matches the beginning of the name of a cipher suite associated with another entity.
  • D. standardizedCipher
    Indicates that an encryption method or cipher conforms to an established, widely accepted standard or specification.
  • E. vulnerableCipherMode
    Indicates that the cryptographic operation uses a cipher mode known to be insecure or susceptible to attacks.
  • F. None of above.

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_69eff6efd1b08190ae3cefd4f11388a2 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f66d7765208190b87b1cc6d96a151c completed May 2, 2026, 9:32 p.m.
PD Predicate disambiguation batch_69f66abfdaf08190a55f14c70be6fd4d completed May 2, 2026, 9:21 p.m.
Created at: April 28, 2026, 1:17 a.m.