Triple
T9931873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brainpool curves |
E192665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elliptic curve family |
C23683
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: elliptic curve family Context triple: [brainpool curves, instanceOf, elliptic curve family]
-
A.
cryptographic parameter set family
chosen
A cryptographic parameter set family is a collection of related parameter sets, typically varying in size or security level, that define the mathematical and operational settings for a class of cryptographic algorithms.
-
B.
finite-field Diffie-Hellman group
A finite-field Diffie-Hellman group is a multiplicative group of integers modulo a prime (or prime power) used as the algebraic setting in which two parties can securely compute a shared secret via the Diffie-Hellman key exchange protocol.
-
C.
curve over the rational numbers
A curve over the rational numbers is an algebraic curve defined by polynomial equations with rational coefficients, considered together with its set of rational solutions and their arithmetic properties.
-
D.
nonsingular curve
A nonsingular curve is an algebraic curve with no singular points, meaning it is smooth everywhere and has a well-defined tangent line at every point.
-
E.
system on a chip family
A system on a chip family is a group of closely related integrated circuits that share a common architecture and design philosophy, each combining multiple computing, memory, and peripheral components on a single chip for different performance, power, and feature needs.
- F. None of above.
Provenance (1 batch)
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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:43 p.m.