Triple
T32515997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secp256k1 |
E831062
|
entity |
| Predicate | implementedInLibrary |
P55160
|
FINISHED |
| Object |
libsecp256k1
libsecp256k1 is a high-performance C library providing cryptographic primitives for the secp256k1 elliptic curve, widely used in Bitcoin and related blockchain applications.
|
E2009239
|
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: libsecp256k1 | Statement: [secp256k1, implementedInLibrary, libsecp256k1]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: libsecp256k1 Triple: [secp256k1, implementedInLibrary, libsecp256k1]
Generated description
libsecp256k1 is a high-performance C library providing cryptographic primitives for the secp256k1 elliptic curve, widely used in Bitcoin and related blockchain applications.
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347066e9688190a3bf35d92413154f |
completed | June 18, 2026, 10:25 p.m. |
| NEDg | Description generation | batch_6a3470eb59888190b257fd4bb4388959 |
completed | June 18, 2026, 10:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a3471aeeafc819095c4c99c29310c4d |
completed | June 18, 2026, 10:31 p.m. |
Created at: May 1, 2026, 1 a.m.