Triple
T15264157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolis |
E364855
|
entity |
| Predicate | affects |
P9
|
FINISHED |
| Object | Ethereum consensus rules |
E1147413
|
NE 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: Ethereum consensus rules | Statement: [Metropolis, affects, Ethereum consensus rules]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ethereum consensus rules Context triple: [Metropolis, affects, Ethereum consensus rules]
-
A.
Ethereum consensus specifications
Ethereum consensus specifications are the formal technical standards that define how Ethereum’s proof-of-stake network reaches agreement on the blockchain’s state and validates blocks.
-
B.
Ethereum consensus layer
chosen
The Ethereum consensus layer is the part of the Ethereum protocol that coordinates validators and block production to securely agree on the canonical blockchain state.
-
C.
Ethereum Beacon Chain protocol
The Ethereum Beacon Chain protocol is the core proof-of-stake consensus layer of Ethereum that coordinates validators, finalizes blocks, and secures the network.
-
D.
Ethereum Yellow Paper
The Ethereum Yellow Paper is the formal technical specification that rigorously defines the Ethereum protocol and its virtual machine for researchers, implementers, and developers.
-
E.
Ethereum Improvement Proposals
Ethereum Improvement Proposals are standardized design documents that define and coordinate technical changes, upgrades, and standards for the Ethereum blockchain ecosystem.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef6fc290819096ef03f8ecae8876 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:14 a.m.