Triple
T32515975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secp256k1 |
E831062
|
entity |
| Predicate | aCoefficient |
P29150
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [secp256k1, aCoefficient, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aCoefficient Context triple: [secp256k1, aCoefficient, 0]
-
A.
coefficientProperty
Indicates a relationship where one entity serves as a coefficient or scalar factor that quantitatively modifies or characterizes another entity or property.
-
B.
coefficientsIn
Indicates that one entity appears as a coefficient within the mathematical expression or representation of another entity.
-
C.
coefficientSystems
Indicates a relationship where specific numerical or algebraic coefficients are assigned or associated with a system, structure, or set of elements.
-
D.
firstCoefficientProperty
chosen
Indicates a property or characteristic specifically associated with the first coefficient in a mathematical or algebraic expression.
-
E.
cofactor
Indicates that one entity functions as a non-protein helper or auxiliary component required for the proper activity of another entity, typically an enzyme or protein.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4a2e4cc81909158364159fac689 |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.