Triple
T25550477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVX-512 |
E640424
|
entity |
| Predicate | mayBeDisabledBy |
P136300
|
FINISHED |
| Object | microcode updates |
—
|
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: microcode updates | Statement: [AVX-512, mayBeDisabledBy, microcode updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDisabledBy Context triple: [AVX-512, mayBeDisabledBy, microcode updates]
-
A.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
-
B.
canBeDeactivatedBy
chosen
Indicates that one entity has the ability or means to deactivate or disable another entity.
-
C.
enabledBy
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
D.
disabledByDefaultIn
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
-
E.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8c583e48190a2a1f65d80a2b589 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:36 p.m.