Triple
T29867894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cuFFT |
E758503
|
entity |
| Predicate | supportsTransformType |
P24486
|
FINISHED |
| Object | complex-to-complex FFT |
—
|
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: complex-to-complex FFT | Statement: [cuFFT, supportsTransformType, complex-to-complex FFT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransformType Context triple: [cuFFT, supportsTransformType, complex-to-complex FFT]
-
A.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
canTransform
Indicates that one entity is capable of being changed or converted into another entity or state.
-
C.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
supportsOutputType
Indicates that one entity is capable of producing, handling, or generating data or results of the specified output type.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:52 p.m.