Triple

T2114500
Position Surface form Disambiguated ID Type / Status
Subject FTP E42574 entity
Predicate usesEncryptionInVariant P5656 FINISHED
Object TLS (in FTPS) E1268 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: TLS (in FTPS) | Statement: [FTP, usesEncryptionInVariant, TLS (in FTPS)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS (in FTPS)
Context triple: [FTP, usesEncryptionInVariant, TLS (in FTPS)]
  • A. TLS chosen
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • B. FTPS
    FTPS is a secure extension of the File Transfer Protocol that adds support for Transport Layer Security (TLS) encryption to protect data in transit.
  • C. SSL
    SSL (Secure Sockets Layer) is a cryptographic protocol designed to provide secure, encrypted communication over a computer network, commonly used to protect data transmitted between clients and servers.
  • 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. STARTTLS
    STARTTLS is a protocol command used to upgrade an existing unencrypted connection to a secure TLS-encrypted one, commonly in email and other text-based communication protocols.
  • 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: usesEncryptionInVariant
Context triple: [FTP, usesEncryptionInVariant, TLS (in FTPS)]
  • A. usesEncryptionAlgorithm chosen
    Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
  • B. requiresEncryption
    Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
  • C. securedVariant
    Indicates that one entity is a security-enhanced or more protected version of another entity.
  • D. hasCrypt
    Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
  • E. encryptionDirection
    Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
  • 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_69ae3076afec819091183e328cff58c8 completed March 9, 2026, 2:29 a.m.
PD Predicate disambiguation batch_69abb7ba08948190a3c236bb53ee4257 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.