Triple
T32707090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabin cryptosystem |
E836301
|
entity |
| Predicate | privateKey |
P174815
|
FINISHED |
| Object | (p, q) |
—
|
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: (p, q) | Statement: [Rabin cryptosystem, privateKey, (p, q)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privateKey Context triple: [Rabin cryptosystem, privateKey, (p, q)]
-
A.
privateKeySize
Indicates the size or length of a private key used in a cryptographic relationship or operation.
-
B.
keyPair
Indicates a relationship where two cryptographic keys are associated as a matched pair, typically consisting of a public key and a corresponding private key used together for secure operations.
-
C.
keyIntermediate
Indicates that something serves as an essential transitional or intermediary step, component, or stage within a larger process or relationship.
-
D.
keyImport
Indicates the action or process of bringing an existing cryptographic key into a system or application for use.
-
E.
keyClient
Indicates that one entity is a primary or strategically important client of 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c851d2488190a93924bca6b167d1 |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.