Triple
T25425433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLMUL |
E637104
|
entity |
| Predicate | instructionForm |
P158493
|
FINISHED |
| Object | PCLMULQDQ xmm, xmm/m128, imm8 |
—
|
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: PCLMULQDQ xmm, xmm/m128, imm8 | Statement: [CLMUL, instructionForm, PCLMULQDQ xmm, xmm/m128, imm8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionForm Context triple: [CLMUL, instructionForm, PCLMULQDQ xmm, xmm/m128, imm8]
-
A.
instructionMode
Indicates the method or medium through which an instruction, lesson, or teaching activity is delivered.
-
B.
instruction
Indicates that one entity provides a directive or order specifying an action that another entity should perform.
-
C.
instructionMnemonic
Indicates that one entity is the mnemonic name or shorthand representation used to denote a particular instruction in an instruction set or language.
-
D.
instructionIssue
Indicates that one entity issues or gives an instruction or directive to another entity.
-
E.
instrumentForm
Indicates that one entity serves as the physical or structural form in which an instrument or tool is realized or embodied for another entity.
- 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_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:57 p.m.