Triple
T5028161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC2 |
E113227
|
entity |
| Predicate | keyExpansion |
P60607
|
FINISHED |
| Object | complex key schedule with 128-entry table |
—
|
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: complex key schedule with 128-entry table | Statement: [RC2, keyExpansion, complex key schedule with 128-entry table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExpansion Context triple: [RC2, keyExpansion, complex key schedule with 128-entry table]
-
A.
ciphertextExpansion
Indicates that applying the encryption process to the input increases its length, specifying how much the ciphertext expands relative to the original data.
-
B.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
C.
keyExperiment
Indicates that an experiment plays a central or pivotal role within a broader study, project, or research context.
-
D.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
E.
keyFormula
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.