Triple
T9931909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | brainpool curves |
E192665
|
entity |
| Predicate | primeFieldSizeRange |
P56108
|
FINISHED |
| Object | 160-bit to 512-bit primes |
—
|
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: 160-bit to 512-bit primes | Statement: [brainpool curves, primeFieldSizeRange, 160-bit to 512-bit primes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primeFieldSizeRange Context triple: [brainpool curves, primeFieldSizeRange, 160-bit to 512-bit primes]
-
A.
usesFiniteField
Indicates that one entity employs or operates within a finite field as part of its structure, computation, or definition.
-
B.
fieldElement
Indicates that one entity is an element or member of a specified field (such as a mathematical or data field).
-
C.
hasPrimeModulus
chosen
Indicates that the associated entity or structure is defined over, or characterized by, a modulus that is a prime number.
-
D.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
E.
nominalKeySize
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.