Triple
T1711915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/MIME |
E37201
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | Secure/Multipurpose Internet Mail Extensions |
E37201
|
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: Secure/Multipurpose Internet Mail Extensions | Statement: [S/MIME, fullName, Secure/Multipurpose Internet Mail Extensions]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Secure/Multipurpose Internet Mail Extensions Context triple: [S/MIME, fullName, Secure/Multipurpose Internet Mail Extensions]
-
A.
S/MIME
chosen
S/MIME is a widely used standard for secure email that provides encryption and digital signatures using public key cryptography.
-
B.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
C.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
D.
RFC 3501
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
-
E.
SMTP
SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa6315afdc81908409435bb47e8ee0 |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8addf4a48190b19cdb861db5eecd |
completed | March 8, 2026, 2:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.