Triple
T15263668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethereum Virtual Machine |
E364845
|
entity |
| Predicate | opcodeSet |
P9897
|
FINISHED |
| Object | arithmetic operations |
—
|
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: arithmetic operations | Statement: [Ethereum Virtual Machine, opcodeSet, arithmetic operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opcodeSet Context triple: [Ethereum Virtual Machine, opcodeSet, arithmetic operations]
-
A.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
B.
instructionSetName
Indicates the specific name assigned to an instruction set associated with an entity or system.
-
C.
instructionSetType
chosen
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
D.
commandSet
Indicates that one entity issues or defines a specific set of commands for another entity or system to follow.
-
E.
instructionSetExtension
Indicates that one instruction set architecture extends or augments another with additional instructions or capabilities.
- 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.