Triple
T15263746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIP-1559 |
E364846
|
entity |
| Predicate | transactionField |
P117844
|
FINISHED |
| Object | maxFeePerGas |
—
|
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: maxFeePerGas | Statement: [EIP-1559, transactionField, maxFeePerGas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transactionField Context triple: [EIP-1559, transactionField, maxFeePerGas]
-
A.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
-
B.
transactionModel
Indicates a relationship where an entity uses or is governed by a specific structured framework or schema for conducting, recording, or managing transactions.
-
C.
foreignTransactionFeature
Indicates that an entity supports or is associated with functionality for handling foreign or international transactions.
-
D.
transactionCounterparty
Indicates that one entity is the other party involved in a financial or commercial transaction with the subject entity.
-
E.
transferPrice
Indicates a relationship where a price is assigned or paid to transfer ownership or control of something from one party to another.
- 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_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. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.