Triple
T30422579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Streaming SIMD Extensions |
E773937
|
entity |
| Predicate | numberOfXMMRegistersIn64bitMode |
P84760
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Streaming SIMD Extensions, numberOfXMMRegistersIn64bitMode, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfXMMRegistersIn64bitMode Context triple: [Streaming SIMD Extensions, numberOfXMMRegistersIn64bitMode, 16]
-
A.
numberOfGeneralPurposeRegisters
Indicates the quantity of general-purpose registers associated with or available in a given computing context.
-
B.
numberOfRegisters
Indicates the total count of registers associated with or contained in a given entity.
-
C.
floatingPointRegisterCount
chosen
Indicates the number of floating-point registers associated with an entity (such as a processor or execution context).
-
D.
opmaskRegisterCount
Indicates the number of operand mask registers involved or required in the operation.
-
E.
nativeModeIndexRegisterSize
Indicates the size of the index register when operating in the system’s native mode.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: April 29, 2026, 8:06 p.m.