Triple
T7304709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSSE3 |
E167944
|
entity |
| Predicate | containsInstructionType |
P9897
|
FINISHED |
| Object | horizontal add and subtract operations |
—
|
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: horizontal add and subtract operations | Statement: [SSSE3, containsInstructionType, horizontal add and subtract operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInstructionType Context triple: [SSSE3, containsInstructionType, horizontal add and subtract operations]
-
A.
instructionSetType
chosen
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
B.
containsProgramType
Indicates that one entity includes or encompasses a specific type or category of program.
-
C.
hasProgramTypeRestriction
Indicates that there is a constraint limiting which types of programs are allowed or applicable in a given context.
-
D.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
E.
hasTypeOfInstrumentation
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd61c0c8190abb1368c9dfb1550 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.