RFC 1452
E222149
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1452 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777475 — 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 1452 Context triple: [RFC 1901, obsoletes, RFC 1452]
-
A.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
B.
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.
-
C.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
D.
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.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files 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 1452 Target entity description: RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
A.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
B.
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.
-
C.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
D.
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.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Network Management ⓘ |
| category | Standards Track ⓘ |
| defines |
coexistence strategy for SNMPv1 and SNMPv2
ⓘ
guidelines for transition from SNMPv1 to SNMPv2 ⓘ |
| documentType | Internet Standard ⓘ |
| focusesOn | coexistence of SNMPv1 and SNMPv2 ⓘ |
| format | text ⓘ |
| hasSuccessor | RFC 1901 ⓘ |
| intendedUse | Internet community ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 1901
ⓘ
STD 16 ⓘ |
| partOf | Internet-standard Network Management Framework ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries | STD ⓘ |
| relatedTo |
SNMP
ⓘ
Simple Network Management Protocol ⓘ
linked to:
SNMP
network management protocols ⓘ |
| relatesToProtocolVersion |
SNMPv1
ⓘ
SNMPv2 ⓘ
linked to:
SNMPv2 standards suite
|
| RFCNumber | 1452 ⓘ |
| standardizes | coexistence mechanisms for SNMP versions ⓘ |
| standardsBody |
IETF Network Management Area
ⓘ
linked to:
IETF Areas
|
| status | Obsoleted ⓘ |
| STDNumber | STD 16 ⓘ |
| title | Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework ⓘ |
| type | technical specification ⓘ |
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 1452 Description of subject: RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.