Triple
T15263764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Merge |
E364847
|
entity |
| Predicate | effectOnMining |
P40373
|
FINISHED |
| Object | eliminated ETH mining on Ethereum mainnet |
—
|
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: eliminated ETH mining on Ethereum mainnet | Statement: [The Merge, effectOnMining, eliminated ETH mining on Ethereum mainnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnMining Context triple: [The Merge, effectOnMining, eliminated ETH mining on Ethereum mainnet]
-
A.
effectOnMachines
Indicates the influence or impact that one entity, condition, or action has on machines and their behavior or performance.
-
B.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
C.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
D.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
- 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.