Triple
T7279129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel SGX |
E163103
|
entity |
| Predicate | instructionSetExtensionOf |
P74574
|
FINISHED |
| Object | Intel x86 ISA |
—
|
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: Intel x86 ISA | Statement: [Intel SGX, instructionSetExtensionOf, Intel x86 ISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionSetExtensionOf Context triple: [Intel SGX, instructionSetExtensionOf, Intel x86 ISA]
-
A.
instructionSetExtension
chosen
Indicates that one instruction set architecture extends or augments another with additional instructions or capabilities.
-
B.
instructionSetExtensions
Indicates that one entity defines, supports, or includes additional instruction set features or extensions relative to another.
-
C.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
D.
instructionSetSize
Indicates the size or number of instructions defined in an instruction set.
-
E.
extendsProgramsOf
Indicates that one program builds upon, enhances, or broadens the scope of another program’s content, features, or capabilities.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.