Triple
T32707103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabin cryptosystem |
E836301
|
entity |
| Predicate | encryptionComplexity |
P28756
|
FINISHED |
| Object | polynomial time in log n |
—
|
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: polynomial time in log n | Statement: [Rabin cryptosystem, encryptionComplexity, polynomial time in log n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionComplexity Context triple: [Rabin cryptosystem, encryptionComplexity, polynomial time in log n]
-
A.
encryptionLevel
Indicates the degree or strength of cryptographic protection applied to data or communications.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
-
D.
encryptionIs
Indicates that one entity serves as the encryption method, state, or property applied to another entity.
-
E.
attackComplexity
Indicates the level of difficulty or effort required by an attacker to successfully exploit a vulnerability or carry out an attack.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:10 a.m.