Triple
T12515635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EdDSA |
E299184
|
entity |
| Predicate | securityBasis |
P3815
|
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: [EdDSA, securityBasis, elliptic curve discrete logarithm problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityBasis Context triple: [EdDSA, securityBasis, elliptic curve discrete logarithm problem]
-
A.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
B.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
C.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
D.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
E.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.