RFC 1436
E804794
RFC 1436 is the Internet standards document that defines the Gopher protocol for distributed document search and retrieval.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1436 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9515381 — 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 1436 Context triple: [Gopher, standardizedIn, RFC 1436]
-
A.
RFC 1446
RFC 1446 is an early Internet standards document that defined mechanisms for managing network devices using the Simple Network Management Protocol (SNMP) before being superseded by later revisions.
-
B.
RFC 1442
RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
-
C.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
D.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
E.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
- 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 1436 Target entity description: RFC 1436 is the Internet standards document that defines the Gopher protocol for distributed document search and retrieval.
-
A.
RFC 1446
RFC 1446 is an early Internet standards document that defined mechanisms for managing network devices using the Simple Network Management Protocol (SNMP) before being superseded by later revisions.
-
B.
RFC 1442
RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
-
C.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
D.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
E.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| accessURL | https://www.rfc-editor.org/rfc/rfc1436 ⓘ |
| area | Applications ⓘ |
| category | Informational RFC ⓘ |
| defines |
Gopher item types
ⓘ
Gopher menu structure ⓘ Gopher selector strings ⓘ Gopher server-client interaction ⓘ Gopher+ extensions overview NERFINISHED ⓘ Internet Gopher Protocol NERFINISHED ⓘ |
| definesProtocol | Gopher protocol NERFINISHED ⓘ |
| describes |
Gopher client behavior
ⓘ
Gopher directory hierarchy NERFINISHED ⓘ Gopher item type codes ⓘ Gopher search queries ⓘ Gopher server behavior ⓘ Gopher+ attribute mechanism (at a high level) ⓘ |
| documents | early Internet information service architecture ⓘ |
| focusesOn | simple, menu-based navigation of distributed documents ⓘ |
| influenced | early web and hypertext information systems design ⓘ |
| intendedAudience |
network application developers
ⓘ
system administrators ⓘ |
| language | English ⓘ |
| protocolType | distributed document search and retrieval protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments ⓘ |
| relatedTo |
FTP
ⓘ
Gopher protocol NERFINISHED ⓘ WAIS NERFINISHED ⓘ World Wide Web NERFINISHED ⓘ |
| rfcNumber | 1436 ⓘ |
| specifies |
CRLF-terminated lines
ⓘ
TCP-based client-server protocol ⓘ line-oriented text responses ⓘ tab-delimited Gopher menu entries ⓘ use of TCP port 70 for Gopher ⓘ use of a single period on a line to terminate a response ⓘ |
| standardizes | Gopher URL access method (pre-URL notation, via selectors and host/port) ⓘ |
| status | Informational ⓘ |
| title | The Internet Gopher Protocol (a distributed document search and retrieval protocol) NERFINISHED ⓘ |
| useCase |
Campus-wide information systems
ⓘ
Wide-area information retrieval ⓘ |
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 1436 Description of subject: RFC 1436 is the Internet standards document that defines the Gopher protocol for distributed document search and retrieval.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.