Triple
T32515998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secp256k1 |
E831062
|
entity |
| Predicate | libsecp256k1Maintainer |
P174539
|
FINISHED |
| Object | Bitcoin Core developers |
—
|
NE NERFINISHED |
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: Bitcoin Core developers | Statement: [secp256k1, libsecp256k1Maintainer, Bitcoin Core developers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: libsecp256k1Maintainer Context triple: [secp256k1, libsecp256k1Maintainer, Bitcoin Core developers]
-
A.
nativeCryptocurrency
Indicates that a cryptocurrency is the primary, built-in medium of exchange and value for a specific blockchain or distributed ledger.
-
B.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
C.
nativeBlockchain
Indicates that a given asset, token, or functionality is inherently built into and originates from a specific blockchain rather than being issued or bridged from another chain.
-
D.
blockReach
Indicates that one block is able to reach or make contact with another block, typically within a defined spatial or interaction range.
-
E.
chainDeveloper
Indicates a relationship where one developer depends on, extends, or builds upon the work or output of another developer in a sequential chain.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.