RFC 3771
E848578
RFC 3771 is an earlier Internet Engineering Task Force (IETF) specification related to Lightweight Directory Access Protocol (LDAP) that was later superseded by RFC 4512.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3771 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T10158250 — 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 3771 Context triple: [RFC 4512, obsoletes, RFC 3771]
-
A.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
D.
RFC 5721
RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
-
E.
RFC 3377
RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
- 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 3771 Target entity description: RFC 3771 is an earlier Internet Engineering Task Force (IETF) specification related to Lightweight Directory Access Protocol (LDAP) that was later superseded by RFC 4512.
-
A.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
D.
RFC 5721
RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
-
E.
RFC 3377
RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
- F. None of above. chosen
Statements (29)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| abbreviatedAs | LDAP ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines | LDAP technical specification ⓘ |
| focusesOn |
LDAP information model
ⓘ
directory schema ⓘ directory services ⓘ |
| format | text ⓘ |
| hasSuccessor | RFC 4512 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4512 ⓘ |
| obsoletes | RFC 3771 ⓘ |
| protocolFamily |
Internet protocol suite
ⓘ
linked to:
TCP/IP
|
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedSpecification |
RFC 4510
ⓘ
RFC 4511 ⓘ RFC 4513 ⓘ RFC 4514 ⓘ RFC 4515 ⓘ RFC 4516 ⓘ RFC 4517 ⓘ RFC 4518 ⓘ RFC 4519 ⓘ |
| relatedToProtocol | Lightweight Directory Access Protocol ⓘ |
| standardsBody |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| standardsOrganization | Internet Society ⓘ |
| status | Obsoleted ⓘ |
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 3771 Description of subject: RFC 3771 is an earlier Internet Engineering Task Force (IETF) specification related to Lightweight Directory Access Protocol (LDAP) that was later superseded by RFC 4512.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.