Triple
T25550407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVX |
E640423
|
entity |
| Predicate | contextSwitchRequirement |
P132557
|
FINISHED |
| Object | extended state management via XSAVE/XRSTOR |
—
|
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: extended state management via XSAVE/XRSTOR | Statement: [AVX, contextSwitchRequirement, extended state management via XSAVE/XRSTOR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextSwitchRequirement Context triple: [AVX, contextSwitchRequirement, extended state management via XSAVE/XRSTOR]
-
A.
switching
Indicates changing from one state, option, or entity to another, replacing the original with a different one.
-
B.
transitionRequirements
chosen
Indicates the conditions or prerequisites that must be satisfied for a change from one state, phase, or status to another to occur.
-
C.
changesRequirement
Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
-
D.
futureChangeRequires
Indicates that a planned or upcoming modification is contingent upon, or must be preceded by, another specified condition, action, or change.
-
E.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 3:36 p.m.