Triple
T9931606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3447 |
E192659
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | EME-PKCS1-v1_5 |
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: EME-PKCS1-v1_5 | Statement: [RFC 3447, defines, EME-PKCS1-v1_5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EME-PKCS1-v1_5 Context triple: [RFC 3447, defines, EME-PKCS1-v1_5]
-
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.
PKCS #7
PKCS #7 is a cryptographic standard that defines the syntax for digitally signing and encrypting data, forming the basis for formats like S/MIME and CMS (Cryptographic Message Syntax).
-
C.
DSA (Digital Signature Algorithm)
DSA (Digital Signature Algorithm) is a widely used public-key cryptographic standard for creating and verifying digital signatures, originally based on principles similar to those of the ElGamal signature scheme.
-
D.
Message-Digest Algorithm 5
Message-Digest Algorithm 5 (MD5) is a widely known but now cryptographically broken hash function that produces a 128-bit hash value and was once commonly used for checksums and data integrity verification.
-
E.
PKCS #12
PKCS #12 is a binary file format used to store and transport cryptographic objects such as private keys, certificates, and related secrets in a secure, interoperable way.
- 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_69d2578e92f08190ba53f943f3da2166 |
completed | April 5, 2026, 12:37 p.m. |
Created at: March 30, 2026, 8:43 p.m.