Triple
T9931584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3447 |
E192659
|
entity |
| Predicate | shortTitle |
P38
|
FINISHED |
| Object | PKCS #1: RSA Cryptography Specifications Version 2.1 |
E37199
|
NE FINISHED |
How this triple was built (2 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: PKCS #1: RSA Cryptography Specifications Version 2.1 | Statement: [RFC 3447, shortTitle, PKCS #1: RSA Cryptography Specifications Version 2.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKCS #1: RSA Cryptography Specifications Version 2.1 Context triple: [RFC 3447, shortTitle, PKCS #1: RSA Cryptography Specifications Version 2.1]
-
A.
PKCS #1
chosen
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
-
B.
Public-Key Cryptography Standards #7
Public-Key Cryptography Standards #7 (PKCS #7) is a widely used cryptographic standard that defines a general syntax for digitally signing and encrypting data, forming the basis for formats like S/MIME.
-
C.
Public-Key Cryptography Standards #8
Public-Key Cryptography Standards #8 (PKCS #8) is a widely used cryptographic standard that defines a syntax for storing and transferring private keys in a secure, interoperable format.
-
D.
IEEE P1363
IEEE P1363 is a public-key cryptography standard developed by the IEEE that specifies a suite of asymmetric algorithms, including those based on elliptic curves, for encryption, digital signatures, and key agreement.
-
E.
RFC 8016
RFC 8016 is an Internet Engineering Task Force (IETF) specification that updates the TURN protocol to improve how it relays traffic for clients behind Network Address Translators (NATs).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cb6276ec8190ad8623129f804c91 |
completed | April 5, 2026, 8:51 p.m. |
Created at: March 30, 2026, 8:43 p.m.