Triple
T27638890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SegWit2x |
E696535
|
entity |
| Predicate | segwitActivationMethod |
P162787
|
FINISHED |
| Object | BIP91 signaling |
—
|
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: BIP91 signaling | Statement: [SegWit2x, segwitActivationMethod, BIP91 signaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segwitActivationMethod Context triple: [SegWit2x, segwitActivationMethod, BIP91 signaling]
-
A.
softForkActivation
chosen
Indicates that a protocol change is being activated in a backward-compatible (soft fork) manner within a blockchain or distributed ledger system.
-
B.
secondHalvingYear
Indicates the calendar year in which the second halving event of a recurring, typically periodic, process or quantity occurs.
-
C.
feeEfficiencyComparedToSegwit
Indicates how the transaction’s fee efficiency compares to that of an equivalent SegWit transaction.
-
D.
chainCharacteristic
Indicates that one entity specifies a characteristic, property, or attribute of a chain associated with another entity.
-
E.
thirdHalvingYear
Indicates the calendar year in which the third occurrence of a recurring halving event (such as a scheduled reduction in rate or quantity) takes place.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:25 p.m.