Triple
T8284198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P (packed-SIMD extension) |
E193751
|
entity |
| Predicate | targetWorkloads |
P22769
|
FINISHED |
| Object | signal processing |
—
|
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: signal processing | Statement: [P (packed-SIMD extension), targetWorkloads, signal processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetWorkloads Context triple: [P (packed-SIMD extension), targetWorkloads, signal processing]
-
A.
targetWork
Indicates that one entity is the specific work (e.g., document, artwork, or project) that another entity is directed at, refers to, or is primarily concerned with.
-
B.
supportsWorkloadType
chosen
Indicates that one entity is capable of handling, operating with, or being compatible with a specified type of workload.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
-
E.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad0535081908bb234cfc0e32b32 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.