Triple
T32515945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST P-256 family |
E831061
|
entity |
| Predicate | basedOnProblem |
P197028
|
FINISHED |
| Object | elliptic curve discrete logarithm problem |
—
|
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: elliptic curve discrete logarithm problem | Statement: [NIST P-256 family, basedOnProblem, elliptic curve discrete logarithm problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnProblem Context triple: [NIST P-256 family, basedOnProblem, elliptic curve discrete logarithm problem]
-
A.
basedOnSolutionOf
Indicates that one entity is derived, developed, or constructed using the solution or outcome produced by another entity.
-
B.
basedOnQuestion
Indicates that something is derived from, informed by, or constructed in response to a specific question.
-
C.
basedOnSubject
Indicates that something is derived from, influenced by, or determined according to a particular subject.
-
D.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
E.
basedOnProcess
Indicates that something is derived from, determined by, or dependent on a particular process or sequence of actions.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: May 1, 2026, 1 a.m.