Triple
T9961876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliptic Curve Digital Signature Algorithm |
E195587
|
entity |
| Predicate | commonlyUsedCurve |
P91679
|
FINISHED |
| Object | secp256k1 |
—
|
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: secp256k1 | Statement: [Elliptic Curve Digital Signature Algorithm, commonlyUsedCurve, secp256k1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsedCurve Context triple: [Elliptic Curve Digital Signature Algorithm, commonlyUsedCurve, secp256k1]
-
A.
relatedCurve
Indicates that one curve is associated with or derived from another curve in a defined relational way.
-
B.
isCurved
Indicates that an object or path deviates smoothly from a straight line, forming a bend or arc.
-
C.
curvePurpose
Indicates that a curve exists or is defined for a particular purpose, function, or intended use.
-
D.
numberOfCurves
Indicates the relationship that specifies how many distinct curves are associated with or contained in a given entity.
-
E.
curveOrder
Indicates the specific sequence or ranking assigned to curves within a set or system.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d37f0c8190946b958c399f3250 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:47 p.m.