Triple
T15263723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIP-1559 |
E364846
|
entity |
| Predicate | replacesMechanism |
P26634
|
FINISHED |
| Object | first-price gas auction |
—
|
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: first-price gas auction | Statement: [EIP-1559, replacesMechanism, first-price gas auction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesMechanism Context triple: [EIP-1559, replacesMechanism, first-price gas auction]
-
A.
replacedOrComplementedMechanism
chosen
Indicates that one mechanism has been superseded by, or now functions alongside as a complement to, another mechanism.
-
B.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
C.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
D.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
E.
revisionMechanism
Indicates the method or process by which something is updated, corrected, or modified over time.
- 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.