Triple
T15264347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besu |
E364860
|
entity |
| Predicate | implements |
P1417
|
FINISHED |
| Object | Ethereum Yellow Paper specification |
E1147408
|
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 Yellow Paper specification | Statement: [Besu, implements, Ethereum Yellow Paper specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ethereum Yellow Paper specification Context triple: [Besu, implements, Ethereum Yellow Paper specification]
-
A.
Ethereum Yellow Paper
chosen
The Ethereum Yellow Paper is the formal technical specification that rigorously defines the Ethereum protocol and its virtual machine for researchers, implementers, and developers.
-
B.
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.
-
C.
Ethereum white paper
The Ethereum white paper is the foundational document authored by Vitalik Buterin that outlines the design and vision for the Ethereum blockchain and its smart contract platform.
-
D.
Ethereum JSON-RPC specification
The Ethereum JSON-RPC specification is the standard interface that defines how external applications communicate with Ethereum nodes to query blockchain data and send transactions.
-
E.
Ethereum Virtual Machine
The Ethereum Virtual Machine is a decentralized, sandboxed runtime that executes smart contracts and enforces the rules of the Ethereum blockchain across a global network of nodes.
- 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.