RFC 977
E239817
RFC 977 is the original specification that standardized the Network News Transfer Protocol (NNTP) used for reading and distributing Usenet news.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 977 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T2114431 — 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: RFC 977 Context triple: [NNTP, definedIn, RFC 977]
-
A.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 877
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
D.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
E.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
- 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: RFC 977 Target entity description: RFC 977 is the original specification that standardized the Network News Transfer Protocol (NNTP) used for reading and distributing Usenet news.
-
A.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 877
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
D.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
E.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 977 self-link ⓘ |
| applicationDomain |
Usenet
ⓘ
Usenet ⓘ
surface form:
Usenet news distribution
|
| area | Application layer ⓘ |
| category | Application protocols ⓘ |
| defaultPort | 119 ⓘ |
| defines |
authentication mechanisms for NNTP
ⓘ
client-server protocol for distributing Usenet news ⓘ client-server protocol for reading Usenet news ⓘ commands for NNTP ⓘ error handling for NNTP ⓘ message formats for NNTP ⓘ response codes for NNTP ⓘ |
| definesOperation |
article posting
ⓘ
article retrieval ⓘ article transfer between servers ⓘ |
| definesRole |
NNTP client
ⓘ
NNTP server ⓘ |
| documentType | Technical specification ⓘ |
| focus | text-based command-response protocol ⓘ |
| influenced |
Usenet news server implementations
ⓘ
Usenet newsreader implementations ⓘ |
| language | English ⓘ |
| layer | Application layer of the Internet protocol suite ⓘ |
| networkModel |
TCP/IP
ⓘ
surface form:
Internet protocol suite
|
| portUsage | uses well-known TCP port 119 by default ⓘ |
| protocolSpecified |
NNTP
ⓘ
NNTP ⓘ
surface form:
Network News Transfer Protocol
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| purpose | to standardize NNTP for reading and distributing Usenet news ⓘ |
| relatedTo |
RFC 3977
ⓘ
SMTP ⓘ
surface form:
Simple Mail Transfer Protocol
Usenet ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| standardized |
posting of news articles to NNTP servers
ⓘ
reading of news articles from NNTP servers ⓘ transfer of news articles between NNTP servers ⓘ |
| status | Proposed standard ⓘ |
| supersededBy | RFC 3977 ⓘ |
| title |
NNTP
ⓘ
surface form:
Network News Transfer Protocol
|
| transportProtocol |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
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: RFC 977 Description of subject: RFC 977 is the original specification that standardized the Network News Transfer Protocol (NNTP) used for reading and distributing Usenet news.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.