Triple

T9548175
Position Surface form Disambiguated ID Type / Status
Subject RFC 1652 E230348 entity
Predicate defines P264 FINISHED
Object SMTP Service Extension for 8-bit MIME transport E805482 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: SMTP Service Extension for 8-bit MIME transport | Statement: [RFC 1652, defines, SMTP Service Extension for 8-bit MIME transport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SMTP Service Extension for 8-bit MIME transport
Context triple: [RFC 1652, defines, SMTP Service Extension for 8-bit MIME transport]
  • A. SMTP Service Extension for 8bit-MIMEtransport chosen
    SMTP Service Extension for 8bit-MIMEtransport is an Internet standard that defines how SMTP can be extended to support the transmission of 8-bit MIME message bodies without requiring conversion to 7-bit format.
  • B. SMTP Service Extension for Secure SMTP over Transport Layer Security
    SMTP Service Extension for Secure SMTP over Transport Layer Security is an IETF standard (RFC 3207) that defines how to use TLS to provide encryption and secure authentication for SMTP email transmissions.
  • C. MIME
    MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
  • D. RFC 3821
    RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
  • E. RFC 3821
    RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
  • 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_69ca847c70b8819088a0a0bad64a50d6 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9904732c8190ab60ecc47c995cbe completed April 1, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1527c0914819087ffa9d201afdd35 completed April 4, 2026, 6:03 p.m.
Created at: March 30, 2026, 8:02 p.m.