Triple
T25616937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD K6-2 |
E642183
|
entity |
| Predicate | supportsMMX |
P85948
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AMD K6-2, supportsMMX, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMMX Context triple: [AMD K6-2, supportsMMX, yes]
-
A.
supportsAVX
Indicates that one entity provides or is compatible with AVX (Advanced Vector Extensions) functionality for another entity or operation.
-
B.
supportsIntel64
Indicates that one entity provides compatibility with or operational support for Intel 64-bit (x86-64) architecture in relation to another entity.
-
C.
SIMDSupport
chosen
Indicates that an entity provides or is compatible with SIMD (Single Instruction, Multiple Data) operations or instruction sets.
-
D.
supportsSuperscalarExecution
Indicates that an architecture or component can execute multiple instructions in parallel within a single clock cycle using superscalar techniques.
-
E.
supportsAVX2
Indicates that one entity provides or has compatibility with AVX2 (Advanced Vector Extensions 2) instruction set capabilities for another.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 21, 2026, 5 p.m.