Triple
T25931692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESENCLAST |
E653452
|
entity |
| Predicate | inputOperandType |
P11909
|
FINISHED |
| Object | XMM register |
—
|
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: XMM register | Statement: [AESENCLAST, inputOperandType, XMM register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputOperandType Context triple: [AESENCLAST, inputOperandType, XMM register]
-
A.
inputType
chosen
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
C.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
-
D.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
-
E.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f604192b6c8190b86e151a628eafd8 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:37 a.m.