Triple
T1711923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/MIME |
E37201
|
entity |
| Predicate | extends |
P1244
|
FINISHED |
| Object | MIME |
E192660
|
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: MIME | Statement: [S/MIME, extends, MIME]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIME Context triple: [S/MIME, extends, MIME]
-
A.
MIME
chosen
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.
-
B.
MIME Sniffing Standard
The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
-
C.
S/MIME
S/MIME is a widely used standard for secure email that provides encryption and digital signatures using public key cryptography.
-
D.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
E.
Media Mail
Media Mail is a discounted U.S. Postal Service shipping option specifically for sending educational materials and media such as books, sound recordings, and DVDs.
- 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_69ada0d1882c81908e02e36ab28e7fdc |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 4, 2026, 7:30 p.m.