Triple
T2555978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Always Encrypted |
E56730
|
entity |
| Predicate | deterministicEncryptionAllows |
P34885
|
FINISHED |
| Object | equality comparisons |
—
|
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: equality comparisons | Statement: [Always Encrypted, deterministicEncryptionAllows, equality comparisons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deterministicEncryptionAllows Context triple: [Always Encrypted, deterministicEncryptionAllows, equality comparisons]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
-
C.
isDeterministicWithFixedNonceAndKey
chosen
Indicates that the outcome of an operation is fully determined and repeatable when the same nonce and key are used, with no additional randomness involved.
-
D.
supportsParallelEncryption
Indicates that the subject is capable of performing encryption operations in parallel, rather than strictly sequentially.
-
E.
supportsParallelDecryption
Indicates that one entity enables or is compatible with decrypting multiple items or data streams simultaneously.
- F. None of above.
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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.