Triple
T15263730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIP-1559 |
E364846
|
entity |
| Predicate | baseFeeAdjustment |
P49246
|
FINISHED |
| Object | increases when blocks are above target gas usage |
—
|
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: increases when blocks are above target gas usage | Statement: [EIP-1559, baseFeeAdjustment, increases when blocks are above target gas usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseFeeAdjustment Context triple: [EIP-1559, baseFeeAdjustment, increases when blocks are above target gas usage]
-
A.
feeMarketChange
chosen
Indicates a change or adjustment in a fee market, such as an update to prevailing fees or fee structure within that market.
-
B.
baseRate
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
-
C.
feedGasSource
Indicates that one entity serves as the supplying source of gas that is fed into another entity or process.
-
D.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
E.
feeEfficiencyComparedToSegwit
Indicates how the transaction’s fee efficiency compares to that of an equivalent SegWit transaction.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.