Triple
T9931919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brainpool curves |
E192665
|
entity |
| Predicate | comparedTo |
P278
|
FINISHED |
| Object | NIST P-384 |
E831966
|
NE 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: NIST P-384 | Statement: [brainpool curves, comparedTo, NIST P-384]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NIST P-384 Context triple: [brainpool curves, comparedTo, NIST P-384]
-
A.
NIST P-256 family
The NIST P-256 family is a widely used set of 256-bit elliptic curves standardized by NIST for secure public-key cryptography and digital signatures.
-
B.
P-384
chosen
P-384 is a NIST-recommended 384-bit elliptic curve widely used for strong cryptographic security in digital signatures and key exchange.
-
C.
Ed448
Ed448 is a modern high-security elliptic-curve digital signature algorithm designed for strong cryptographic assurance and efficient performance.
-
D.
P-521
P-521 is a NIST-recommended 521-bit elliptic curve over a prime field widely used for high-security digital signatures in ECDSA.
-
E.
Curve448
Curve448 is a high-security elliptic curve designed for modern cryptographic protocols, particularly for efficient and secure key exchange and digital signatures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2578e92f08190ba53f943f3da2166 |
completed | April 5, 2026, 12:37 p.m. |
Created at: March 30, 2026, 8:43 p.m.