Triple
T25616918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD K6-2 |
E642183
|
entity |
| Predicate | introducedInstructionSetExtension |
P74581
|
FINISHED |
| Object | 3DNow! |
—
|
NE NERFINISHED |
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: 3DNow! | Statement: [AMD K6-2, introducedInstructionSetExtension, 3DNow!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInstructionSetExtension Context triple: [AMD K6-2, introducedInstructionSetExtension, 3DNow!]
-
A.
instructionSetExtension
Indicates that one instruction set architecture extends or augments another with additional instructions or capabilities.
-
B.
instructionSetExtensions
chosen
Indicates that one entity defines, supports, or includes additional instruction set features or extensions relative to another.
-
C.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
D.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
E.
kernelInterfaceIntroduced
Indicates that a new interface has been added or exposed within the kernel.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 5 p.m.