Triple
T25425482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel TSX-NI |
E637105
|
entity |
| Predicate | usesInstructionPrefix |
P93740
|
FINISHED |
| Object | XACQUIRE |
—
|
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: XACQUIRE | Statement: [Intel TSX-NI, usesInstructionPrefix, XACQUIRE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInstructionPrefix Context triple: [Intel TSX-NI, usesInstructionPrefix, XACQUIRE]
-
A.
hasInstructionPrefix
Indicates that one entity provides an initial segment or starting portion that serves as the instruction prefix for another entity.
-
B.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
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.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
E.
commandPrefix
Indicates that one entity serves as the leading sequence of characters (prefix) used to invoke or recognize commands associated with another entity.
- 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_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:57 p.m.