Triple
T25425432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLMUL |
E637104
|
entity |
| Predicate | opcodeName |
P2980
|
FINISHED |
| Object | PCLMULQDQ |
—
|
NE NERFINISHED |
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 | Statement: [CLMUL, opcodeName, PCLMULQDQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opcodeName Context triple: [CLMUL, opcodeName, PCLMULQDQ]
-
A.
instructionSetName
Indicates the specific name assigned to an instruction set associated with an entity or system.
-
B.
operationCodeName
chosen
Indicates that an operation is associated with a specific code name used to identify or refer to it.
-
C.
operationName
Indicates the specific action or procedure being performed or invoked within a process or system.
-
D.
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.
-
E.
commandName
Indicates the specific label or identifier used to denote a particular command within a system or interface.
- 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_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_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:57 p.m.