Triple

T25425485
Position Surface form Disambiguated ID Type / Status
Subject Intel TSX-NI E637105 entity
Predicate usesInstruction P69226 FINISHED
Object XEND
XEND is an Intel TSX (Transactional Synchronization Extensions) instruction that marks the successful end of a hardware transaction region.
 E1681087 NE FINISHED

How this triple was built (3 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: XEND | Statement: [Intel TSX-NI, usesInstruction, XEND]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: XEND
Triple: [Intel TSX-NI, usesInstruction, XEND]
Generated description
XEND is an Intel TSX (Transactional Synchronization Extensions) instruction that marks the successful end of a hardware transaction region.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: usesInstruction
Context triple: [Intel TSX-NI, usesInstruction, XEND]
  • A. includesInstruction chosen
    Indicates that one entity contains, provides, or embeds an instruction or set of instructions directed toward another entity.
  • B. canInstruct
    Indicates that one entity has the authority or ability to give instructions or guidance to another entity.
  • C. usesInstrument
    Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
  • D. supportsInstruction
    Indicates that one entity provides assistance, resources, or functionality that enables or facilitates the instruction or teaching activities of another entity.
  • E. usesDirective
    Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
  • F. None of above.

Provenance (6 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_69f6135293908190809e255bf6334760 completed May 2, 2026, 3:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10899c570881908096628a9552cef9 completed May 22, 2026, 4:51 p.m.
NEDg Description generation batch_6a108a66ebfc8190843d591e9ab47493 completed May 22, 2026, 4:55 p.m.
NED2 Entity disambiguation (via description) batch_6a108b266a648190874a4e80f1df2bb8 completed May 22, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69f611a72780819082f44e66ca2c6ac9 completed May 2, 2026, 3 p.m.
Created at: April 21, 2026, 1:57 p.m.