Triple
T7279357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenCL |
E163108
|
entity |
| Predicate | supportsExecutionOn |
P11903
|
FINISHED |
| Object | CPU |
—
|
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: CPU | Statement: [OpenCL, supportsExecutionOn, CPU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExecutionOn Context triple: [OpenCL, supportsExecutionOn, CPU]
-
A.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
B.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
C.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
D.
operationSupported
Indicates that a particular operation is available and can be performed or handled by a given entity or system.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.