Triple

T11502608
Position Surface form Disambiguated ID Type / Status
Subject SMTP Service Extension for Secure SMTP over Transport Layer Security E272699 entity
Predicate instanceOf P0 FINISHED
Object email security protocol specification C995 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: email security protocol specification
Context triple: [SMTP Service Extension for Secure SMTP over Transport Layer Security, instanceOf, email security protocol specification]
  • A. email authentication protocol extension
    An email authentication protocol extension is an add-on specification that enhances existing email authentication mechanisms (such as SPF, DKIM, or DMARC) to provide additional security, policy control, or interoperability features for verifying the legitimacy of email messages.
  • B. network security protocol chosen
    A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
  • C. POP3 specification
    The POP3 specification defines the protocol and rules by which email clients connect to mail servers to retrieve, authenticate, and manage messages from a user's mailbox over a TCP/IP network.
  • D. cryptographic protocol message
    A cryptographic protocol message is a structured unit of data exchanged between parties in a cryptographic protocol, containing information such as identifiers, nonces, keys, and signatures to achieve security goals like confidentiality, integrity, and authentication.
  • E. cryptographic protocol
    A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
  • F. None of above.

Provenance (1 batch)

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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 9:36 p.m.