Triple
T28901658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA256SU0 |
E732965
|
entity |
| Predicate | opcodeClass |
P165508
|
FINISHED |
| Object | SHA-256 schedule update instruction |
—
|
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: SHA-256 schedule update instruction | Statement: [SHA256SU0, opcodeClass, SHA-256 schedule update instruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opcodeClass Context triple: [SHA256SU0, opcodeClass, SHA-256 schedule update instruction]
-
A.
operatorClass
Indicates the classification or category of an operator in terms of its type, role, or functional group within a system or domain.
-
B.
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.
-
C.
operatorClassName
Indicates the classification or type name assigned to an operator within a system or model.
-
D.
instructionMnemonic
Indicates that one entity is the mnemonic name or shorthand representation used to denote a particular instruction in an instruction set or language.
-
E.
hasOpcode
Indicates that an instruction or operation is associated with a specific opcode value that encodes its behavior.
- F. None of above. chosen
Provenance (4 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 8:03 a.m.