Triple
T25425244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDSEED |
E637100
|
entity |
| Predicate | cpuidLeaf |
P158289
|
FINISHED |
| Object | CPUID.(EAX=07H, ECX=0):EBX.RDSEED[bit 18] |
—
|
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: CPUID.(EAX=07H, ECX=0):EBX.RDSEED[bit 18] | Statement: [RDSEED, cpuidLeaf, CPUID.(EAX=07H, ECX=0):EBX.RDSEED[bit 18]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cpuidLeaf Context triple: [RDSEED, cpuidLeaf, CPUID.(EAX=07H, ECX=0):EBX.RDSEED[bit 18]]
-
A.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
-
B.
cpuImplementation
Indicates that one entity serves as the hardware or architectural realization (implementation) of a specified CPU design or model.
-
C.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
D.
cpuBits
Indicates the number of bits used by a CPU’s architecture or word size in the described context.
-
E.
cpuArchitecture
Indicates the type of processor instruction set or hardware architecture that a computing system or component is designed to run on.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:57 p.m.