RFC 2256
E826112
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T9865289 — 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 2256 Context triple: [RFC 4517, obsoletes, RFC 2256]
-
A.
RFC 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
-
B.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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 2256 Target entity description: RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
A.
RFC 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
-
B.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- F. None of above. chosen
Statements (65)
| Predicate | Object |
|---|---|
| instanceOf |
LDAP specification
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| basedOn |
ITU-T Recommendation X.500(1996)
ⓘ
linked to:
X.500
|
| category | Standards Track ⓘ |
| defines |
attributeType businessCategory
ⓘ
attributeType c (countryName) ⓘ attributeType cn (commonName) ⓘ attributeType description ⓘ attributeType destinationIndicator ⓘ attributeType employeeNumber ⓘ attributeType employeeType ⓘ attributeType facsimileTelephoneNumber ⓘ attributeType generationQualifier ⓘ attributeType givenName ⓘ attributeType initials ⓘ attributeType internationalISDNNumber ⓘ attributeType l (localityName) ⓘ attributeType labeledURI ⓘ attributeType mail ⓘ attributeType o (organizationName) ⓘ attributeType ou (organizationalUnitName) ⓘ attributeType owner ⓘ attributeType physicalDeliveryOfficeName ⓘ attributeType postOfficeBox ⓘ attributeType postalCode ⓘ attributeType preferredDeliveryMethod ⓘ attributeType preferredLanguage ⓘ attributeType registeredAddress ⓘ attributeType seeAlso ⓘ attributeType sn (surname) ⓘ attributeType st (stateOrProvinceName) ⓘ attributeType street ⓘ attributeType telephoneNumber ⓘ attributeType teletexTerminalIdentifier ⓘ attributeType telexNumber ⓘ attributeType userPassword ⓘ attributeType x121Address ⓘ objectClass country in LDAPv3 schema ⓘ objectClass dcObject in LDAPv3 schema ⓘ objectClass groupOfNames in LDAPv3 schema ⓘ objectClass groupOfUniqueNames in LDAPv3 schema ⓘ objectClass locality in LDAPv3 schema ⓘ objectClass organization in LDAPv3 schema ⓘ objectClass organizationalPerson in LDAPv3 schema ⓘ objectClass organizationalUnit in LDAPv3 schema ⓘ objectClass person in LDAPv3 schema ⓘ objectClass residentialPerson in LDAPv3 schema ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 4517
ⓘ
RFC 4519 ⓘ |
| protocolFamily | LDAP ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
LDAPv3
ⓘ
linked to:
Lightweight Directory Access Protocol
|
| RFCNumber | 2256 ⓘ |
| specifies |
LDAP user schema
ⓘ
X.500(1996) user schema subset for LDAPv3 ⓘ |
| standardFor |
Internet
ⓘ
linked to:
the internet
|
| status | Obsoleted ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supersededBy |
RFC 4517
ⓘ
RFC 4519 ⓘ |
| title | A Summary of the X.500(96) User Schema for use with LDAPv3 ⓘ |
| updates | LDAPv2 schema usage to LDAPv3 ⓘ |
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 2256 Description of subject: RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.