RFC 3652
E346320
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3652 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T3267184 — 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 3652 Context triple: [Handle System, standardizedAs, RFC 3652]
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
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 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.
-
E.
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.
- 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 3652 Target entity description: RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
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 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.
-
E.
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.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track document ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
mechanisms for assigning handles
ⓘ
mechanisms for managing handles ⓘ mechanisms for resolving handles ⓘ |
| describes |
Handle System
ⓘ
surface form:
Handle System naming architecture
Handle System protocol operations ⓘ Handle System service model ⓘ |
| documentType | technical specification ⓘ |
| focusesOn |
global resolution infrastructure
ⓘ
persistence of digital identifiers ⓘ |
| intendedUse | Internet-wide persistent identification ⓘ |
| language | English ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| relatedTo |
digital object identifiers
ⓘ
distributed identifier resolution ⓘ persistent digital identifiers ⓘ |
| rfcNumber | 3652 ⓘ |
| specifies |
Handle System for persistent identifiers
ⓘ
Handle protocol ⓘ
surface form:
Handle System protocols
Handle System technical architecture ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| standardsTrackFor | Handle System ⓘ |
| status | Standards Track ⓘ |
| subjectOf | Handle System ⓘ |
| title |
Handle System
ⓘ
surface form:
Handle System Overview
|
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 3652 Description of subject: RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.