RFC 1909
E276198
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1909 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T1814064 — 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 1909 Context triple: [RFC 3410, obsoletes, RFC 1909]
-
A.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
B.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
C.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
D.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
E.
RFC 1592
RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations 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 1909 Target entity description: RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
A.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
B.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
C.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
D.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
E.
RFC 1592
RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations before being superseded by later RFCs.
- F. None of above. chosen
Statements (26)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track document ⓘ |
| abbreviation | RFC1909 ⓘ |
| area | Network Management ⓘ |
| category | Standards Track ⓘ |
| defines | administrative model for SNMPv2 ⓘ |
| documentType | technical specification ⓘ |
| focusesOn | network management ⓘ |
| governingBody | Internet Engineering Steering Group ⓘ |
| hasNumber | 1909 ⓘ |
| isPartOf |
Internet standards process
ⓘ
linked to:
IETF Internet standards process
|
| language | English ⓘ |
| obsoletedBy | RFC 3410 ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| partOf |
SNMPv2 framework
ⓘ
linked to:
SNMPv2 standards suite
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
SNMP
ⓘ
Simple Network Management Protocol ⓘ
linked to:
SNMP
|
| relatedToProtocol |
SNMPv2
ⓘ
linked to:
SNMPv2 standards suite
|
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| standardizes | administrative infrastructure for SNMPv2 ⓘ |
| status | Obsoleted ⓘ |
| successor | RFC 3410 ⓘ |
| title | An Administrative Infrastructure for SNMPv2 ⓘ |
| updates | SNMPv2 administrative framework ⓘ |
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 1909 Description of subject: RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.