DATA command
E207722
The DATA command is an SMTP protocol instruction used to indicate that the following lines constitute the content of an email message, including its headers and body.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DATA command canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1866866 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DATA command Context triple: [RFC 5321, specifies, DATA command]
-
A.
Home Command
Home Command was a major British Army formation responsible for the administration, training, and home defence of forces within the United Kingdom.
-
B.
Media Independent Command Service
Media Independent Command Service is a component of the IEEE 802.21 framework that provides a standardized way for higher-layer protocols to control and manage handovers across heterogeneous network technologies.
-
C.
Meta AI assistant
Meta AI assistant is an artificial intelligence–powered virtual assistant created by Meta to help users with tasks like answering questions, generating content, and interacting across Meta’s platforms.
-
D.
Command
Command is a behavioral design pattern that encapsulates a request as an object, allowing parameterization, queuing, logging, and support for undoable operations.
-
E.
Support Command
Support Command was a former organizational formation within a military structure that provided logistical and operational support functions before being succeeded by a field army.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DATA command Target entity description: The DATA command is an SMTP protocol instruction used to indicate that the following lines constitute the content of an email message, including its headers and body.
-
A.
Home Command
Home Command was a major British Army formation responsible for the administration, training, and home defence of forces within the United Kingdom.
-
B.
Media Independent Command Service
Media Independent Command Service is a component of the IEEE 802.21 framework that provides a standardized way for higher-layer protocols to control and manage handovers across heterogeneous network technologies.
-
C.
Meta AI assistant
Meta AI assistant is an artificial intelligence–powered virtual assistant created by Meta to help users with tasks like answering questions, generating content, and interacting across Meta’s platforms.
-
D.
Command
Command is a behavioral design pattern that encapsulates a request as an object, allowing parameterization, queuing, logging, and support for undoable operations.
-
E.
Support Command
Support Command was a former organizational formation within a military structure that provided logistical and operational support functions before being succeeded by a field army.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
SMTP command
ⓘ
email protocol instruction ⓘ |
| abbreviationFor | DATA ⓘ |
| appliesTo |
message body
ⓘ
message headers ⓘ |
| belongsToLayer | application layer ⓘ |
| canBeUsedWith | ESMTP extensions ⓘ |
| definedIn | RFC 5321 ⓘ |
| follows |
MAIL command
ⓘ
RCPT command ⓘ |
| hasBehavior |
server reads message data until terminator is received
ⓘ
server returns final completion status after terminator ⓘ |
| hasConstraint |
lines starting with a dot are dot-stuffed
ⓘ
message data ends only with <CRLF>.<CRLF> ⓘ |
| hasHistoricalStandard | RFC 821 ⓘ |
| hasKeyword | DATA ⓘ |
| hasPhaseName | DATA phase ⓘ |
| hasProperty |
may be rejected with 5xx reply codes
ⓘ
must be sent after at least one valid RCPT TO ⓘ subject to size limits enforced by server ⓘ |
| hasReplyExample | 354 Start mail input; end with <CRLF>.<CRLF> ⓘ |
| hasRole |
indicate start of email content
ⓘ
separate SMTP envelope from message content ⓘ |
| hasSecurityConsideration |
can be used to send spam
ⓘ
may be scanned for malware ⓘ subject to content filtering ⓘ |
| hasSyntax | DATA<CRLF> ⓘ |
| partOf |
SMTP
ⓘ
surface form:
Simple Mail Transfer Protocol
|
| precedes | end-of-data terminator ⓘ |
| processedBy | SMTP server ⓘ |
| relatedTo |
MAIL FROM command
ⓘ
QUIT command ⓘ RCPT TO command ⓘ RSET command ⓘ |
| replacedSpecificationOf | RFC 2821 ⓘ |
| requires |
at least one successful RCPT TO command
ⓘ
successful MAIL FROM command ⓘ |
| sentBy | SMTP client ⓘ |
| startsPhase | message data phase ⓘ |
| triggerResponseCode | 354 ⓘ |
| usedFor |
transmitting MIME-encoded content
ⓘ
transmitting full RFC 5322 message ⓘ |
| usedIn | SMTP transaction ⓘ |
| usedInContext |
email delivery between MTAs
ⓘ
email relay ⓘ email submission ⓘ |
| usesTerminator | <CRLF>.<CRLF> ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: DATA command Description of subject: The DATA command is an SMTP protocol instruction used to indicate that the following lines constitute the content of an email message, including its headers and body.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.