Triple
T32542112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiener’s attack on RSA |
E831738
|
entity |
| Predicate | recovers |
P107880
|
FINISHED |
| Object | private exponent d |
—
|
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: private exponent d | Statement: [Wiener’s attack on RSA, recovers, private exponent d]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recovers Context triple: [Wiener’s attack on RSA, recovers, private exponent d]
-
A.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
-
B.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
C.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
D.
reconstructs
Indicates performing an action to rebuild, restore, or reassemble something from its parts, damage, or prior state.
-
E.
recoveredThrough
chosen
Indicates that something was regained, restored, or obtained again by means of a specified method, process, or intermediary.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57f14348190a0e2b98597e5ba25 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.