Triple
T25425267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDSEED |
E637100
|
entity |
| Predicate | statusOnUnsupportedCPU |
P31509
|
FINISHED |
| Object | invalid opcode exception (#UD) |
—
|
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: invalid opcode exception (#UD) | Statement: [RDSEED, statusOnUnsupportedCPU, invalid opcode exception (#UD)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnUnsupportedCPU Context triple: [RDSEED, statusOnUnsupportedCPU, invalid opcode exception (#UD)]
-
A.
supportsNEON
Indicates that one entity provides or enables NEON (ARM Advanced SIMD) instruction set support for another entity.
-
B.
unsupportedPlatform
chosen
Indicates that a given platform is not supported for a particular action, feature, or system.
-
C.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
D.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
-
E.
numericCoprocessorSupport
Indicates that a system or processor includes and can utilize a dedicated numeric coprocessor for performing arithmetic or mathematical operations.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:57 p.m.