Triple
T3267182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handle System |
E68554
|
entity |
| Predicate | standardizedAs |
P1371
|
FINISHED |
| Object |
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.
|
E341325
|
NE FINISHED |
How this triple was built (4 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: RFC 3650 | Statement: [Handle System, standardizedAs, RFC 3650]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3650 Context triple: [Handle System, standardizedAs, RFC 3650]
-
A.
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.
-
B.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
-
C.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
D.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
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.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 3650 Triple: [Handle System, standardizedAs, RFC 3650]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3650 Target entity description: 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.
-
A.
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.
-
B.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
-
C.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
D.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
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
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafce46dc8190a157e4f5012baed5 |
completed | March 8, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b28ef261ec819091c62620765e2cef |
completed | March 12, 2026, 10:01 a.m. |
| NEDg | Description generation | batch_69b28f9efe408190bcb1e16931b2fe62 |
completed | March 12, 2026, 10:04 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b2a8b873b081909bbb5de329e45169 |
completed | March 12, 2026, 11:51 a.m. |
Created at: March 8, 2026, 3:09 p.m.