Triple
T21192951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDCP |
E522254
|
entity |
| Predicate | appliesCipheringTo |
P143502
|
FINISHED |
| Object | user plane PDUs |
—
|
LITERAL 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: user plane PDUs | Statement: [PDCP, appliesCipheringTo, user plane PDUs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesCipheringTo Context triple: [PDCP, appliesCipheringTo, user plane PDUs]
-
A.
requiresBlockCipher
Indicates that performing this operation or protocol depends on the use of a block cipher as its underlying cryptographic primitive.
-
B.
blockCipherMode
Indicates the specific operational mode used by a block cipher to process data (e.g., how blocks are chained, padded, or transformed during encryption/decryption).
-
C.
ciphertextExpansion
Indicates that applying the encryption process to the input increases its length, specifying how much the ciphertext expands relative to the original data.
-
D.
handledCipherSystem
Indicates that an entity has operated, managed, or otherwise worked with a particular cipher system.
-
E.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:07 p.m.