Triple
T32258969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenstra elliptic-curve factorization method |
E824095
|
entity |
| Predicate | randomized |
P83418
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lenstra elliptic-curve factorization method, randomized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: randomized Context triple: [Lenstra elliptic-curve factorization method, randomized, true]
-
A.
isRandomized
chosen
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
B.
introducesRandomnessIn
Indicates that something adds an element of unpredictability or variability into another process, system, or outcome.
-
C.
randomizationMethod
Indicates the procedure or technique used to randomly assign subjects or units to different groups or conditions in a study or experiment.
-
D.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
E.
stochastic
Indicates that the relationship or process involves randomness or probabilistic behavior rather than being fully deterministic.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc5652e08190b519631b7d497e75 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:41 a.m.