Triple
T8936765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4954 |
E212795
|
entity |
| Predicate | extends |
P1244
|
FINISHED |
| Object | ESMTP |
E5622
|
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: ESMTP | Statement: [RFC 4954, extends, ESMTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESMTP Context triple: [RFC 4954, extends, ESMTP]
-
A.
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.
-
B.
SMTP
chosen
SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across IP networks.
-
C.
SMTP AUTH
SMTP AUTH is an extension to the Simple Mail Transfer Protocol that enables client authentication to mail servers, helping prevent unauthorized use and spam.
-
D.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
E.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b3628881909544507628980c25 |
completed | April 1, 2026, 12:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1e692548190b631c4926927d12f |
completed | April 3, 2026, 1:34 p.m. |
Created at: March 30, 2026, 6:58 p.m.