Triple
T28612827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SH-1 |
E724208
|
entity |
| Predicate | usesInstructionEncoding |
P112755
|
FINISHED |
| Object | fixed-length 16-bit instructions |
—
|
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: fixed-length 16-bit instructions | Statement: [SH-1, usesInstructionEncoding, fixed-length 16-bit instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInstructionEncoding Context triple: [SH-1, usesInstructionEncoding, fixed-length 16-bit instructions]
-
A.
instructionEncoding
chosen
Indicates how an instruction is represented or encoded into a specific formal or machine-readable format.
-
B.
instructionMnemonic
Indicates that one entity is the mnemonic name or shorthand representation used to denote a particular instruction in an instruction set or language.
-
C.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
D.
hasInstructionCache
Indicates that an entity possesses or is equipped with an instruction cache for storing and accessing executable instructions.
-
E.
instructionMode
Indicates the method or medium through which an instruction, lesson, or teaching activity is delivered.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 4:30 a.m.